U++ forum: Welcome to the forum

Search on this site

Search in forums

Home » Extra libraries, Code snippets, applications etc. » C++ language problems and code snippets » Pre processor and macro error

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Pre processor and macro error [message #55685]

Mon, 30 November 2020 15:22

Xemuth
Messages: 387
Registered: August 2018
Location: France

Senior Member

I am working on GLFW package, I want it to be cross platforme, so as plugin/png I did this kind of trick (only pay attention to Windows part):

According to this image, my "glfw3.h" is interpreted after having defined the target (_GLFW_WIN32)

In "glfw3.h" the file internal.h get included and have this following block of code :

#if defined(_GLFW_COCOA)
 #include "cocoa_platform.h"
#elif defined(_GLFW_WIN32)
 #include "win32_platform.h"
#elif defined(_GLFW_X11)
 #include "x11_platform.h"
#elif defined(_GLFW_WAYLAND)
 #include "wl_platform.h"
#elif defined(_GLFW_OSMESA)
 #include "null_platform.h"
#else
 #error "No supported window creation API selected"
#endif

A this point, on my computer, the flag _GLFW_WIN32 should have been set but it's not the case. I don't get why

so here come my question, why when having this block :

#if defined(_WIN32)
	#define _GLFW_WIN32 1
#elif defined(_APPLE)
	#define _GLFW_COCOA 1
#elif defined(_LINUX)
	#define _GLFW_X11 1
#elif defined(_WAYLAND)
	#define _GLFW_WAYLAND 1
#elif define(_OMESA)
	#define _GLFW_OMESA 1
#endif

and being on W10 compiling with CLANG or MSVS don't result in _GLFW_WIN32 being set ? What I am missing ?

Thanks in advance
Xemuth

Report message to a moderator

Re: Pre processor and macro error [message #55695 is a reply to message #55685]

Mon, 30 November 2020 21:54

Klugier
Messages: 1085
Registered: September 2012
Location: Poland, Kraków

Senior Contributor

Hello Xemuth,

Please noticed that GLFW uses CMake as a build system. One of the initial step of this build to is to generate platform specific build basing on CMakeList.txt files. So, I think the flags are generated in this steps, so in our case we need to workaround it if we would like to port it our build system.

So, in your case, all you need to do is to add dependency to upp/Core and in file when flags are defined add something like that:

#include <Core/config.h>

#if defined(PLATFORM_WIN32)
	#define _GLFW_WIN32 1
#elif defined(PLATFORM_COCOA)
	#define _GLFW_COCOA 1
#elif defined(PLATFORM_POSIX)
	#define _GLFW_X11 1
#elif defined(flagWAYLAND) // <- Not supported yet, however you could still pass it as package specific flag
	#define _GLFW_WAYLAND 1
#elif define(flagOMESA) // <- Not supported yet - I don't know what OMESA is? Is it some kind of software rendering?
	#define _GLFW_OMESA 1
#endif

Backing to Wayland here is the documentation how to distinguish it on GTK side. Would be good to have it defined somewhere.

Also, if everything will work as expected please consider make the glfw package available in UppHub Smile

If you do not want to use Core/config.h. You could port it like this:


#if defined(flagWIN32)
	#define _GLFW_WIN32 1
#elif defined(flagCOCOA)
	#define _GLFW_COCOA 1
#elif defined(flagX11)
	#define _GLFW_X11 1
#elif defined(flagWAYLAND) // <- Not supported yet, however you could still pass it as package specific flag
	#define _GLFW_WAYLAND 1
#elif define(flagOMESA) // <- Not supported yet - I don't know what OMESA is? Is it some kind of software rendering?
	#define _GLFW_OMESA 1
#endif

And then GLFW should accepts WIN32 COCOA X11 WAYLAND OMESA and in the package (application) that use that package all you need to do is manually specify flag in "Main package configuration(s)" dialog.

Klugier

U++ - one framework to rule them all.

[Updated on: Mon, 30 November 2020 22:04]

Report message to a moderator

Re: Pre processor and macro error [message #55698 is a reply to message #55695]

Tue, 01 December 2020 11:49

Xemuth
Messages: 387
Registered: August 2018
Location: France

Senior Member

Hello Klugier,

Thanks for your awnser !

I will dig use of <Core/config.h> and try to reproduce all flag Cmake generate depending on configuration.

-WAYLAND, I had never meet any computer using it yet(according to Ubuntu wiki Wayland is a new protocol that enables 3D compositors to be used as primary display servers, instead of running the 3D compositor as an extension under the (2D) X.org display server.) I guess I just have to provide file to GLFW when the system is compatible Wayland, I will try to implement it

-MESA and not 'OMESA' I misspelled it Very Happy

(according to MESA home site The Mesa project began as an open-source implementation of the OpenGL specification - a system for rendering interactive 3D graphics.) Same as Wayland, I will implement it.

Quote:

please consider make the glfw package available in UppHub

I decided to make my GLFW package (which only worked on Windows) cross-platform when I saw the UppHub announcement in order to share it ! (I also want to share my custom 'game engine' but it's another story Razz

)

Report message to a moderator

Previous Topic:	strange MinGw return
Next Topic:	Read a text file and assign values to variables int and double

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Dec 14 14:01:21 CET 2024

Total time taken to generate the page: 0.02075 seconds