Just trying to get terminology to the point, note that developers
from other platforms will most probably have known the term
"linker script", so let's expand on that knowledge without
driving away newbies.
Alexandre Duret-Lutz wrote:
All these examples ought be backed up with test cases, but I
hav
> platform dependent parts present in the ".libs" subdirectory.
(or "_libs" on platforms where filenames cannot start with a '.')
Tim Van Holder wrote:
platform dependent parts present in the ".libs" subdirectory.
(or "_libs" on platforms where filenames cannot start with a '.')
s|".libs"|".libs"/"_libs"|
:-)=)
btw, s|general concept|generalized concept| ?
-- guidohttp://AC-Archive.sf.
On Wed, 2003-07-30 at 09:30, Guido Draheim wrote:
> Just trying to get terminology to the point, note that developers
> from other platforms will most probably have known the term
> "linker script", so let's expand on that knowledge without
> driving away newbies.
FYI: I find the term "linker scrip
Ralf Corsepius wrote:
On Wed, 2003-07-30 at 09:30, Guido Draheim wrote:
Just trying to get terminology to the point, note that developers
from other platforms will most probably have known the term
"linker script", so let's expand on that knowledge without
driving away newbies.
FYI: I find the t
>>> "Harlan" == Harlan Stenn <[EMAIL PROTECTED]> writes:
[...]
Harlan> and immediately wondered if one could say:
Harlan> lib_LTLIBRARIES = libhello.la
Harlan> libhello_la_SOURCES = hello-common.c
Harlan> if LINUX
Harlan> libhello_la_SOURCES+= hello-linux.c
Harlan> else
Harlan> libhello_l
>>> "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes:
Tim> Mainly a few minor language nits;
Thanks a lot!
[...]
>> with a message such as
>> object `foo.lo' created both with libtool and without
Tim> Shouldn't the message be that foo.$(OBJEXT) is created in both cases?
Tim> The progra
>>> "gd" == Guido Draheim <[EMAIL PROTECTED]> writes:
gd> Just trying to get terminology to the point, note that developers
gd> from other platforms will most probably have known the term
gd> "linker script", so let's expand on that knowledge without
gd> driving away newbies.
Hi Guido! Thank
Here is a second version of this section, so that we have
something cleaner in the archives. Beside including comments
from Guido, Harlan, and Tim, I've split the whole section into
shorter nodes (it was all on one node), and added a section
about `ltmain.sh not found'.
(Tim I'll post the Texinfo
Hi,
Andrew Suffield <[EMAIL PROTECTED]> writes:
> On Mon, Jul 28, 2003 at 05:55:15PM -0500, Raja R Harinath wrote:
>> Andrew Suffield <[EMAIL PROTECTED]> writes:
[snip autoreconf/autopoint/AM_GNU_GETTEXT([external]) dicussion]
>> > All that does is stop including a complete copy of libintl in y
Alexandre, greetings,
On Wednesday, July 30, 2003, at 06:40 PM, Alexandre Duret-Lutz wrote:
Here is a second version of this section, so that we have
This looks great -- it's very clear indeed. As an ignorant user, I'm
much more confident that I know what's going on. I have a few comments.
--
On Wed, Jul 30, 2003 at 03:27:37PM -0500, Raja R Harinath wrote:
> >> > All that does is stop including a complete copy of libintl in your
> >> > source tree. autopoint still wants to add a few dozen files. The best
> >> > solution is to not run autopoint at all, since it doesn't do anything
> >> >
I'm quite new to the autotools but working with a small project. I want
to be able to choose that the compilation should compile all files with
the "-g" so I can use gdb on the compiled software...
My files so far is looking like this:
configure.in
-
AC_INIT(musidab, [0.1])
AM_INIT_AUTOMAKE(
>>> "Norman" == Norman Gray <[EMAIL PROTECTED]> writes:
Norman> Alexandre, greetings,
Norman> On Wednesday, July 30, 2003, at 06:40 PM, Alexandre Duret-Lutz wrote:
>> Here is a second version of this section, so that we have
Norman> This looks great -- it's very clear indeed. As an ignoran
Hello,
I ran into the following problem and couldn't find a solution to it on the
net.
Basically i setup automake for use with my project and it works fine so
far. For except one annoying thing. When i actually "make" it, the object
files (.o) and library files get placed in the same direcotry
>>> "Corn" == Corn Hulio <[EMAIL PROTECTED]> writes:
[...]
Corn> Basically i setup automake for use with my project and it works fine
Corn> so far. For except one annoying thing. When i actually "make" it, the
Corn> object files (.o) and library files get placed in the same direcotry
Corn> wh
>>> "juman" == juman <[EMAIL PROTECTED]> writes:
[...]
juman> Any tips of how I easiest disable the compilation from
juman> using the -O2 flag temporary?
Run
./configure CFLAGS=-g
--
Alexandre Duret-Lutz
17 matches
Mail list logo
