Hi (and thx for the reply) Am 28.12.2011 23:50, schrieb JonY: > LDFLAGS is very much autotools specific (avoid custom Makefiles if > possible). Your custom Makefile might not respect LDFLAGS env var. You > need to dive in and understand it before being able to edit it > correctly. I'm guessing you didn't link to glibmm, or your glibmm > install is broken in some way. Look for your hello.exe target link > rule and add the proper link libraries.
Youre right, i dont use Autotools and i dont use gtk-config Tool to automate things.Iam developing right now on Windows with a Console and an Editor. There is nothing broken, the Includ path in the Makefiles has to be set correctly. For Headers it works, but it cannot find the Libs. For Example: In MS-Visual C/C++ i can add in the Project properties / Linker Section wsock32.lib and the MS Compiler will link against it, but how do i this step in g++ ?? There are no *.LIB Files, so what is the correct File? Should i add *.dll.a Files in the /package/lib/ Folder? Autotools. Is Autotools in the MinGW64 Release included right now (on Win64)? Me and Make. Iam very intrested in understanding the GNU Makesystem and it has alot more of cool Features then QMake or MSBuild and its fun to play with it, but for now i only have to know how the MinGW64 Linker must be prepared for finding the libs on Windows in general and in special from within a Makefile. Greetings Peter ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
