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