On Wed, 2006-01-04 at 16:34 -0600, Matt Hull wrote:
> thanks, i think i got that kinda working.
>
> but now its compiling out of order. i have src/main.c that calls the
> gtkmain() in src/gtk-2.0/gtkmain.c it tries to compile src/main.c first
> and fails.
Nope ...
> gcc -DHAVE_CONFIG_H -I. -I
hi, I'm sort of new to the autotools, I'm sending this
to both the automake and autoconf lists as I'm quite
sure which to send to.
I was wondering if it is possible to get quieter
makefile output during compilation? I am currently
using automake 1.9.6 and autoconf 2.59 in debian
unstable, and my
thanks, i think i got that kinda working.
but now its compiling out of order. i have src/main.c that calls the
gtkmain() in src/gtk-2.0/gtkmain.c it tries to compile src/main.c first
and fails.
gcc -DHAVE_CONFIG_H -I. -I. -I.. -Igtk-2.0 -c main.c
gcc-o mine main.o -L/usr/lib -lgtk -lg
Stepan Kasal wrote:
That principle could rather be achieved by omitting the *.c file
from the distribution, supposing that every "customer" can install
the tools which are required to generate it.
Not every customer wants to install developer tools. In general,
people who install a project ju
Hello,
On Wed, Jan 04, 2006 at 06:27:28PM +, Harlan Stenn wrote:
> How about using a "bootstrap script" (or something that gets put
> into config.status) that touches your .c file?
it would have to touch all the intermidiate files first, and then
the *.c file... Urghhh...
Have a nice day,
Hi,
On Wed, Jan 04, 2006 at 10:18:46AM -0800, Bruce Korb wrote:
> Remove the generation of the .c files from your make files.
> Put that logic in "bootstrap" and remove it from Makefile.am.
> It makes life easier. If you distribute "bootstrap", any
> "customer" can run the script, if they so choo
Hello,
On Wed, Jan 04, 2006 at 06:12:11PM +0100, Sander Niemeijer wrote:
> distdir: $(DISTFILES)
> $(am__remove_distdir)
> mkdir $(distdir)
> --->$(mkdir_p) $(distdir)/$(top_srcdir)/data
The problem is caused by the following line in Makefile.am:
EXTRA_DIST = $(top_sr
Hi Sander,
* Sander Niemeijer wrote on Wed, Jan 04, 2006 at 06:12:11PM CET:
>
> I think I have found a bug in automake.
I agree that this is a bug.
> The problem is triggered by configuring the foo-1.0 package using a
> full path to configure (or to use a build directory that differs from
>
I expect that Automake conditionals with traditional make rules for
the intermediate targets wrapped up in a conditional will do the
trick. If you use Automake's maintainer-mode feature, then you can
use
if MAINTAINER_MODE
foo.c : foo.bar
dosomething
endif
There is also a MAINTAINER_TA
Hello,
On Wed, Jan 04, 2006 at 01:15:23PM +0100, Peter Ekberg wrote:
> .INTERMEDIATE: $(FOOBARS) splunk.foobar
[...]
> Is there a portable solution to my needs?
a distributed file cannot depend on a non-distributed one.
So you have to replace the rule
.foobar.c:
./foobar < $< > $@
by
$
How about using a "bootstrap script" (or something that gets put
into config.status) that touches your .c file?
H
Peter Ekberg wrote:
Hello!
I have the following needs:
1. Extract some data from a list of files using script foo.
2. Process the data further using a second script bar.
3. Concatenate the processed data.
4. Run a third script foobar on the concatenation to
produce a .c file.
5. Distribute t
Hi all,
I think I have found a bug in automake.
Attached is an example that reproduces the problem.
The problem is triggered by configuring the foo-1.0 package using a
full path to configure (or to use a build directory that differs from
the source directory) and running a 'make dist'.
If
Hi Adnan,
* Adnan Shaheen wrote on Wed, Jan 04, 2006 at 02:56:03PM CET:
> I want to know how can I put all of the .o files in a specified
> folder, using makefile.am
Yes.
mkdir build
cd build
../path/to/source-tree/configure [OPTIONS]
make
All object files will be below the build directory.
Ch
Hello!
I have the following needs:
1. Extract some data from a list of files using script foo.
2. Process the data further using a second script bar.
3. Concatenate the processed data.
4. Run a third script foobar on the concatenation to
produce a .c file.
5. Distribute the generated .c file,
Hi Adnan,
* Adnan Shaheen wrote on Wed, Jan 04, 2006 at 10:28:01AM CET:
>
> I wrote a manual makefile and it compiles every thing without any problem.
> Than I used the automake and compiled the same project, with one file
> that was used to seek on hard disk, it gives me the following error.
>
I want to know how can I put all of the .o files in a specified
folder, using makefile.am
Thanx
--
Regards:
Adnan Shaheen.
+92-333-962-7637
Software Engineer,
AyeSoft,Islamabad, Pakistan.
Hi all, I was first writing makefile for my project manually, But then
some body told me about the automake process, since then I ve been
using the automake utility to compile and build my projects
I wrote a manual makefile and it compiles every thing without any problem.
Than I used the automake
Hello,
On Wed, Jan 04, 2006 at 01:07:50AM -0600, Matt Hull wrote:
> SUBDIRS = src cli-fe @GTK@
use Automake conditionals:
SUBDIRS = src cli-fe
if WITH_GTK
SUBDIRS += gtk
endif
See the Automake manual for details.
Have a nice day,
Stepan
19 matches
Mail list logo
