0 Members and 1 Guest are viewing this topic.
I tested with MinGW but didn't encounter the problem.
-Wall -Wextra -Wwrite-strings -Wstrict-prototypes
-ansi -O2 -Wchar-subscripts -Wcomment -Wformat=2 -Wimplicit-int -Werror-implicit-function-declaration -Wmain -Wparentheses -Wsequence-point -Wreturn-type -Wswitch -Wtrigraphs -Wunused -Wuninitialized -Wunknown-pragmas -Wfloat-equal -Wundef -Wshadow -Wpointer-arith -Wbad-function-cast -Wwrite-strings -Wconversion -Wsign-compare -Waggregate-return -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wmissing-noreturn -Wformat -Wmissing-format-attribute -Wno-deprecated-declarations -Wpacked -Wredundant-decls -Wnested-externs -Winline -Wlong-long -Wunreachable-code
I have successfully build a Node Addon whit your bindings. However I'm not using the `sf::Init` but the individual `InitP*` functions.
Yes, that makes sense. You don't need any of the networking code as node.js already has it all.
About that, I would like a more "decoupled" bindings, I still have to link the network library even if I don't use it.
Regarding node.js, wouldn't something like this work?void Init( v8::Handle<v8::Object> target ) { target->SetPrototype(sf_v8::sf::Init());}
If you would like I can wrap all the network stuff with #ifndef NO_SFML_NETWORK so that you can exclude it through a define.