On Sunday 19 February 2006 18:32, Rafael Fernández López wrote: > That is one of the reasons because I would like to write my own > Makefile.am. But lots of questions came to my mind, like if I have > something like: > > myproject > src > gui > base > sounds > [...] > > And my objective is only an executable (no .so...) is it necessary to go > on creating *.la files for each directory (and portion of code) to get them > linked at the end of the build process? I'm not sure what you mean. As a matter of fact your entire question is strange. If you wnat to use autoconf/automake and don't want to use KDevelop then you are going to have to read the info pages for autoconf and automake. You will also need to find out what the m4 tests are for QT versions and kdelibs versions if you need that sort of dependency. Makefile.am is only part of the puzzle here.
Your above section here doesn't make much sense either. If you don't want to build libraries in your subdirs you don't have to. You can build all the object files and then link them all together at the end of the build process. If you are creating a custom Makefile you can do whatever you please. > I had some vtable errors from GCC that I had never had before (because > before I used to write my own Makefiles) [no autotools]. What sort of vtable issues? A little more information and a clearer statement of what you are trying to do would be very helpful. -- Zac Slade -- gentoo-user@gentoo.org mailing list
