On Sunday 2023-03-26 14:33, Labeeb Asari wrote:
>
>Basically : compile .c source files with gcc, .cu files with nvcc and
>finally link them together with gcc.
>
>I've tried adding a rule to handle .cu files differently and it does create
>object files for it separately. However while linking, lib
On 01/25/18 04:07, Jay K wrote:
I have a bunch of C.
I want to move to C++.
I'm using automake.
I don't want to rename any files.
that's unwise and not going to serve you well in the long run. I very much
advise against not renaming files converted from C to C++. While it can be done,
this is
> Here's a ping for Ralph.
I asked for his help and then I went and spelled his name wrong. My
apologies Ralf.
-DB
On Friday September 4th, 2009, Eric Blake wrote:
> According to David Byron on 8/14/2009 1:57 PM:
>
> > I'm not sure whether this is something I'm doing wrong
> > or something wrong with automake, autoconf or libtool.
> > At the moment I'm leaning to autoconf + automake.
>
> compile is maintained
On 10/16/07, Bob Friesenhahn <[EMAIL PROTECTED]> wrote:
> On Tue, 16 Oct 2007, NightStrike wrote:
>
> > Where is $(COMPILE) documented? When should it be used? What does it
> > actually get set to?
>
> Read a generated Makefile and all secrets will be revealed.
Looks like here's my answer:
COMP
On 10/16/07, Bob Friesenhahn <[EMAIL PROTECTED]> wrote:
> On Tue, 16 Oct 2007, NightStrike wrote:
>
> > Where is $(COMPILE) documented? When should it be used? What does it
> > actually get set to?
>
> Read a generated Makefile and all secrets will be revealed. Normally
> you should not care abo
On Tue, 16 Oct 2007, NightStrike wrote:
Where is $(COMPILE) documented? When should it be used? What does it
actually get set to?
Read a generated Makefile and all secrets will be revealed. Normally
you should not care about $(COMPILE) since Automake takes care of it.
Bob
===
On 10/16/07, Benoit SIGOURE <[EMAIL PROTECTED]> wrote:
> On Oct 16, 2007, at 10:05 AM, NightStrike wrote:
>
> > Where is $(COMPILE) documented?
>
> http://www.gnu.org/software/automake/manual/html_node/Program-
> variables.html#index-COMPILE-494
>
> > When should it be used?
>
> When you want to "c
On Oct 16, 2007, at 10:05 AM, NightStrike wrote:
Where is $(COMPILE) documented?
http://www.gnu.org/software/automake/manual/html_node/Program-
variables.html#index-COMPILE-494
When should it be used?
When you want to "compile a C source file" (quoting the manual).
Maybe this works fo
* Ralf Wildenhues wrote on Tue, Nov 15, 2005 at 07:37:50AM CET:
>
> noinst_PROGRAMS = program.elf program.bin
> program_elf_SOURCES = main.c
>
> program.bin$(EXEEXT): program.elf
> $(OBJCOPY) -O binary program.elf program.bin
Gaah, that should've been
$(OBJCOPY) -O binary program.e
* Harlan Stenn wrote on Tue, Nov 15, 2005 at 12:08:26AM CET:
> * Heiko Panther wrote:
> > Trying the following gives me an error.
> >
> > noinst_PROGRAMS = program.elf program.bin
> > program_elf_SOURCES = main.c
> >
> > program.bin: program.elf
> > $(OBJCOPY) -O binary program.elf program.bi
Use:
noinst_PROGRAMS = program.elf
noinst_SCRIPTS = program.bin
H
--
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi!
>
> Trying the following gives me an error.
>
> noinst_PROGRAMS = program.elf program.bin
> program_elf_SOURCES = main.c
>
> program.bin: program.elf
> $(OBJCOP
Hi Harald,
* Harald Dunkel wrote on Sun, Nov 13, 2005 at 06:44:12PM CET:
> Ralf Wildenhues wrote:
> >
> > Please consider this thread:
> > http://lists.gnu.org/archive/html/libtool/2005-10/msg00069.html
>
> How is this thread related to copying a missing script?
It shows that your patch is not
i have Makefile.am like this, and it didn't ask for `compile' script
during `configure'.
bin_PROGRAMS = test
test_SOURCES = c.c cc.cc
both sources is empty file.
On 11/14/05, Harald Dunkel <[EMAIL PROTECTED]> wrote:
> Ralf Wildenhues wrote:
> > Hi Harald,
> >
> >
> > Please consider this t
Ralf Wildenhues wrote:
> Hi Harald,
>
>
> Please consider this thread:
> http://lists.gnu.org/archive/html/libtool/2005-10/msg00069.html
>
How is this thread related to copying a missing script? Please
note that C support is broken, too, as soon as there is some
C++ code in your Makefile.am.
Hi Harald,
* Harald Dunkel wrote on Sun, Nov 13, 2005 at 12:00:18PM CET:
> Harald Dunkel wrote:
> >
> > What is the criteria for copying the compile script into
> > the source directory tree? I have some *.cc code, it is
> > mentioned in my Makefile.am file, configure detects that
> > the compile
Hi folks,
Harald Dunkel wrote:
> Hi folks,
>
> What is the criteria for copying the compile script into
> the source directory tree? I have some *.cc code, it is
> mentioned in my Makefile.am file, configure detects that
> the compile script must be used, too, but Automake doesn't
> provide it.
>
> "Harald" == Harald Dunkel <[EMAIL PROTECTED]> writes:
Harald> What is the criteria for copying the compile script into
Harald> the source directory tree? I have some *.cc code, it is
Harald> mentioned in my Makefile.am file, configure detects that
Harald> the compile script must be used, too
Stepan Kasal wrote:
>
> I looked at /usr/share/automake-1.9/compile and I cannot understand
> how this could happen.
> I think that the parametr to compile should look like
> some/path/main.c
> which becomes cfile, and then cofile is assigned as
>
> cofile=`echo "$cfile" | sed -e 's|^.*/||'
Hi Stepan,
Stepan Kasal wrote:
>
> I looked at /usr/share/automake-1.9/compile and I cannot understand
> how this could happen.
> I think that the parametr to compile should look like
> some/path/main.c
> which becomes cfile, and then cofile is assigned as
>
> cofile=`echo "$cfile" | sed -
Stepan Kasal wrote:
> I think that the parametr to compile should look like
>some/path/main.c
> which becomes cfile, and then cofile is assigned as...
Just guessing, but with cl.exe being Bill's C compiler, it
probably doesn't understand `some/path/main.c' as a path name;
(it will
Hallo!
Ralf Wildenhues wrote:
> Alexandre Duret-Lutz writes:
>
> "Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
>> because AM_PROG_CC_C_O horribly
>> overwrites CC, it's not clear to me whether
>>
>> AM_PROG_CC_C_O
>> LT_INIT
>>
>> is equivalent to
>>
>> LT_INIT
>> AM_PROG_CC_C_O
>>
>>
Salut Alexandre!
Alexandre Duret-Lutz wrote:
"Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
>
> Gary> My feeling at the moment is that it would be a small price to pay for
> Gary> simplifying the interface to automake (i.e. _not_ being sometimes told,
> Gary> partway through the auto
Alexandre Duret-Lutz writes:
"Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
Gary> But for a project built with `make -j', we still need AM_PROG_CC_C_O
Gary> and _LT_COMPILER_C_O to understand each others' locks :-(
Seems so. I thought it was not needed because when
AM_PROG_CC_C_O decid
>>> "Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
[...]
Gary> I'm not saying that the compile script should be used,
Gary> just that the tests to determine whether it might be
Gary> needed are run as a matter of course. Looking at the
Gary> implementation of AM_PROG_CC_C_O, I see that
>>> "Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
Gary> But for a project built with `make -j', we still need AM_PROG_CC_C_O
Gary> and _LT_COMPILER_C_O to understand each others' locks :-(
Seems so. I thought it was not needed because when
AM_PROG_CC_C_O decides `compile' is required, i
On Fri, 10 Sep 2004, Gary V. Vaughan wrote:
If the compile script is unnecessarily used, then compilation will be
even slower. This seems particularly true for the Windows operating
system where compilation using libtool already feels like compiling in
molasses. It seems that Windows is very slow
Bob Friesenhahn wrote:
> On Fri, 10 Sep 2004, Gary V. Vaughan wrote:
>
>>
>> Okay. But for a project built with `make -j', we still need
>> AM_PROG_CC_C_O
>> and _LT_COMPILER_C_O to understand each others' locks :-(
>>
>>> [...]
>>>
>>> Gary> Meant to ask, why doesn't AM_INIT_AUTOMAKE (condition
Alexandre Duret-Lutz wrote:
"Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
>
> [...]
>
> Gary> So does that simply mean that libtool objects can be correctly built
> Gary> as subdir-objects without AM_PROG_CC_C_O? Sorry to bug you, just
> Gary> making sure I understand why you made
On Fri, 10 Sep 2004, Gary V. Vaughan wrote:
Okay. But for a project built with `make -j', we still need AM_PROG_CC_C_O
and _LT_COMPILER_C_O to understand each others' locks :-(
[...]
Gary> Meant to ask, why doesn't AM_INIT_AUTOMAKE (conditionally if
Gary> necessary) simply invoke AM_PROG_CC_C_O?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Salut!
On 7 Sep 2004, at 22:03, Alexandre Duret-Lutz wrote:
"Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
Gary> Do we need to patch automake to accept LT_INIT for
Gary> subdir-objects projects, or do you think AC_PROG_CC_C_O
Gary> should be me
>>> "Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
[...]
Gary> So does that simply mean that libtool objects can be correctly built
Gary> as subdir-objects without AM_PROG_CC_C_O? Sorry to bug you, just
Gary> making sure I understand why you made the patch the way you did...
The purpos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Salut Alexandre!
Welcome back. Hope you enjoyed your vacation :-)
On 7 Sep 2004, at 22:03, Alexandre Duret-Lutz wrote:
"Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
[...]
On Mon, Aug 23, 2004 at 08:29:07PM +0100, Patrick Welche wrote:
I just tri
>>> "Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
[...]
>>> On Mon, Aug 23, 2004 at 08:29:07PM +0100, Patrick Welche wrote:
>>>
I just tried to build cvs libtool with cvs auto* all from today, and get:
make all-recursive
Making all in .
>>> cd . && /bin/ksh /us
Hi Alexandre!
Your automake patch of 2004-08-04 causes this to happen:
Noah Misch wrote:
> On Wed, Aug 25, 2004 at 07:51:01PM +0100, Patrick Welche wrote:
>
>>On Mon, Aug 23, 2004 at 08:29:07PM +0100, Patrick Welche wrote:
>>
>>>I just tried to build cvs libtool with cvs auto* all from today, an
>>> "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
Hi Richard,
>>> "Richard" == Richard Boulton <[EMAIL PROTECTED]> writes:
> --- ChangeLog 2002/03/07 21:06:29 1.1780
> +++ ChangeLog 2002/03/10 15:52:11
> @@ -1,3 +1,9 @@
> +2002-03-10 Richard Boulton <[EMAIL PROTECTED]>
> +
> + * automake.in (check_typos): Allow variables with reserved
On Sun, 2002-03-10 at 12:05, Stephan Kulow wrote:
> These bogus errors are caused by automake 1.6 - 1.5 works fine.
I've been getting this too, with Gstreamer.
The problem is that you're using variables with suffices like _LDFLAGS,
which automake interprets specially, and complains about if it d
On Sonntag, 10. März 2002 11:53, Frans Englich wrote:
> If I run 'make -f Makefile.cvs' in a just checked out module(ie kdelibs) I
> get errors looking like this:
>
> This Makefile is only for the CVS repository
> This will be deleted before making the distribution
> *** Creating acinclude.m4
> !!
> "Eric" == Eric Lemings <[EMAIL PROTECTED]> writes:
Eric> I have a directory that contains only source files that I only
Eric> want to compile when I do a make all. What should I put in the
Eric> Makefile.am file?
I don't understand what you mean.
Do you mean that you don't want to link?
40 matches
Mail list logo
