Re: Problem with distribution of bin_SCRIPTS
Am Dienstag, den 29.05.2007, 09:58 +0100 schrieb Noah Slater: > In my package I would like to generate a script from a source file by > simply copying it and setting the executable bit. I do not need to > distribute the script though, only the source. > > No matter how hard I try I cannot get automake to work using the > following set-up: > > * The script source is distributed > * The script is NOT distributed but is generated from the source I guess then you want to use noinst_SCRIPTS or BUILT_SOURCES instead of bin_SCRIPTS. Regards, Daniel
Re: automake and cl.exe
Quoting Ranjith TV <[EMAIL PROTECTED]>: Hi, Can I override using AC_PROG_CXX(or any other compiler checking stuff) Actually I am using automake in windows and I want to use cl(microsoft's) as the compiler I don't want to use like "AC_PROG_CXX(cl g++)" as it requires the path to the compiler and the library to set, which I will be doing in the Makefile.am Hi what about ./configure CXX=cl.exe ? -- Benoit Sigoure aka Tsuna EPITA Research and Development Laboratory This message was sent using IMP, the Internet Messaging Program.
automake and cl.exe
Hi, Can I override using AC_PROG_CXX(or any other compiler checking stuff) Actually I am using automake in windows and I want to use cl(microsoft's) as the compiler I don't want to use like "AC_PROG_CXX(cl g++)" as it requires the path to the compiler and the library to set, which I will be doing in the Makefile.am my directory structure will be like below root build (all files required to build the software, including configure.in) linux32 (makefile.am for linux) win32 (makefile.am for windows, here I will be setting library path and whatever else required) src (all the source code) include regards, Ranjith T V
Re: Problem with distribution of bin_SCRIPTS
Hey, Do you know about VPATH builds? Yes, what an idiot I was not to consider this. You also made a typo, (s/CLEAN_FILES/CLEANFILES/) but make distcheck would have revealed this problem too. Ah yes, it was doing - I wonder how that slipped in there. I also recommend passing the `foreign' option to AM_INIT_AUTOMAKE so that you don't have to supply all these empty files. Don't worry, the example looks nothing like my package - I only put all those files there to keep automake quite. Thanks for the tip though. Thanks for your help... it's working great now! Best, Noah -- "Creativity can be a social contribution, but only in so far as society is free to use the results." - R. Stallman
Re: Problem with distribution of bin_SCRIPTS
Quoting Noah Slater <[EMAIL PROTECTED]>: Hello, Hi, In my package I would like to generate a script from a source file by simply copying it and setting the executable bit. I do not need to distribute the script though, only the source. No matter how hard I try I cannot get automake to work using the following set-up: * The script source is distributed * The script is NOT distributed but is generated from the source I have attached a very small example package that reproduces the problem. If you run "make distcheck" you should get the following error: cp --preserve foo.py foo cp: cannot stat `foo.py': No such file or directory This is dispite foo.py being listed in EXTRA_DIST. Any help is greatly appreciated... Do you know about VPATH builds? It's when sources are in one (possibly read-only) tree and the build takes place in another tree. When you run make distcheck, it actually performs a VPATH build. It turns out that your Makefile does not handle VPATH builds because it assumes that foo.py is in the current directory whereas it's not the case. You also made a typo, (s/CLEAN_FILES/CLEANFILES/) but make distcheck would have revealed this problem too. The attached patch solves your problem. I also recommend passing the `foreign' option to AM_INIT_AUTOMAKE so that you don't have to supply all these empty files. Cheers, -- Benoit Sigoure aka Tsuna EPITA Research and Development Laboratory This message was sent using IMP, the Internet Messaging Program. diff -u -r example/Makefile.am example.mine/Makefile.am --- example/Makefile.am 2007-05-29 10:47:16.0 +0200 +++ example.mine/Makefile.am2007-05-29 11:19:15.0 +0200 @@ -1,9 +1,9 @@ bin_SCRIPTS = foo -CLEAN_FILES = $(bin_SCRIPTS) +CLEANFILES = $(bin_SCRIPTS) EXTRA_DIST = foo.py -foo: foo.py - cp --preserve foo.py foo +foo: $(srcdir)/foo.py + cp --preserve $(srcdir)/foo.py foo chmod +x foo
