From: Zac Slade <krakrjak@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] AUTOTOOLS
Date: Sun, 19 Feb 2006 23:44:17 -0600 [thread overview]
Message-ID: <200602192344.17611.krakrjak@volumehost.net> (raw)
In-Reply-To: <200602200132.06079.info@maestroprogramador.com>
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
next prev parent reply other threads:[~2006-02-20 5:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 0:19 [gentoo-user] [OT] AUTOTOOLS Rafael Fernández López
2006-02-20 0:32 ` Rafael Fernández López
2006-02-20 5:44 ` Zac Slade [this message]
2006-02-20 18:45 ` Rafael Fernández López
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200602192344.17611.krakrjak@volumehost.net \
--to=krakrjak@volumehost.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox