On 12/29/2011 07:17, Peter Meyer wrote: > 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)? >
Oh boy, looks like you skipped some manuals. Use -lfoo to link to libfoo.dll.a, libfoo.a or foo.lib. -L is equivalent to your LIBPATH in MSVC. Please at least look at the GNU GCC and LD manual. Autotools is a shell program to generate configure/makefile.in etc, configure in this case is also a shell script. A base install of Windows will not have anything to run or interpret the shell script, you'll need to install Cygwin, MSYS or Interix. The easiest way to get it all in one place is to use Cygwin and its setup program, simply pick and choose what you want to install, and use the provided mingw-w64 cross compiler to build your program. As for wsock32, it is now relegated to a forwarder DLL to ws2_32.dll, it is strange use wsock32 deliberately these days. It might have problems with some newer WINSOCK API versions, but I'm not sure of this. > 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. > I wouldn't say autotools is the perfect solution for everything, but it is the very best if you are looking for platform portability, especially when you start dealing with shared libraries. Afaik, the sanctioned way to ask for gtkmm library flags is to query it from pkg-config. You'll probably need to work that into your makefile somehow
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ 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
