how to exclude the COPYING file
Hi, I'm writing to ask how to exclude the COPYING file from the distribution. When I type "make dist", the distribution will automatically contain that file. However, the license of my software is in the LICENSE file, and I don't want the GNU GPL in COPYING. Thanks, Presario
Re: how to exclude the COPYING file
Hello Presario, * Presario Smith wrote on Fri, Dec 08, 2006 at 10:15:33AM CET: > > I'm writing to ask how to exclude the COPYING file from the > distribution. When I type > "make dist", the distribution will automatically contain that file. > However, the license of my software is in the LICENSE file, and I > don't want the GNU GPL in COPYING. Don't have a COPYING file lying around in your source tree at 'make dist' time. Use the `foreign' Automake option to not require it, either as automake --foreign or as option argument to AM_INIT_AUTOMAKE in configure.ac, or assign it to the variable AUTOMAKE_OPTIONS in the toplevel Makefile.am. To list the set of files which automake distributes automatically if found, type automake --help Hope that helps. Cheers, Ralf
Re: how to exclude the COPYING file
Hi Ralf, I followed your instructions. I put in my main Makefile.am this line: AUTOMAKE_OPTIONS = foreign And it did the job that I wanted. Many thanks! Best, Presario On 12/8/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: Hello Presario, * Presario Smith wrote on Fri, Dec 08, 2006 at 10:15:33AM CET: > > I'm writing to ask how to exclude the COPYING file from the > distribution. When I type > "make dist", the distribution will automatically contain that file. > However, the license of my software is in the LICENSE file, and I > don't want the GNU GPL in COPYING. Don't have a COPYING file lying around in your source tree at 'make dist' time. Use the `foreign' Automake option to not require it, either as automake --foreign or as option argument to AM_INIT_AUTOMAKE in configure.ac, or assign it to the variable AUTOMAKE_OPTIONS in the toplevel Makefile.am. To list the set of files which automake distributes automatically if found, type automake --help Hope that helps. Cheers, Ralf
Re: no rule to make asm targets
Hello again, I am sorry that I have to post again but I am still stuck with this problem. Was it so that the problem should have been fixed after changing the code to use the global target flags? I hope I have just done something wrong now, but I need to know in order to figure what to try next. Do you have any suggestion for solving this issue, can I post other files? Thank you. Jari. From: Stepan Kasal <[EMAIL PROTECTED]> To: Jari Strand <[EMAIL PROTECTED]> CC: automake@gnu.org Subject: Re: no rule to make asm targets Date: Wed, 6 Dec 2006 11:52:19 +0100 Hello, On Wed, Dec 06, 2006 at 06:21:09AM +0200, Jari Strand wrote: > >For example, does bin_PROGRAMS really contain only one program? > > Yes, [...] OK, in that case there is no need to use per-target flags. Let me show an example: bin_PROGRAMS = first second third first_SOURCES = first.c second_SOURCES = second.c third_SOURCES = third.c AM_CFLAGS = ... second_CFLAGS = ... In this example, `AM_CFLAGS' is used for all programs, with one exception: when compiling program `third', `third_CFLAGS' is used instead. This `third_CFLAGS' is called per-target variable, and overrides the corresponding general one AM_CFLAGS. The mechanism is the same in your case, when you are using *_CPPFLAGS instead of *_CFLAGS. Since you have only one program, you can set `AM_CPPFLAGS' as needed for the program `editorD', and there is no need to use the override mechanism. Then, because of some internal mechanisms of Automake, the suffix rule `.asm.o' will be used, and you can redefine it if you like. Start with the following code, adding back the things you removed to simplify the example. > >bin_PROGRAMS = editorD > >TLIB_PATH = /home > >AM_CPPFLAGS = -I$(TLIB_PATH)/openal/LINUX -I$(TLIB_PATH)/lungif \ > > -I$(TLIB_PATH)/lungif -I$(TLIB_PATH)/opengl2d3d \ > > -I$(TLIB_PATH)/zlib -I$(TLIB_PATH)/lpng -I$(TLIB_PATH)/ljpeg \ > > -I$(TLIB_PATH)/vorbis/include -DEDITOR_BUILD > >editorD_SOURCES = someSource.cc someAsm.asm > >.asm.o: > > $(NASM_PATH) -o $@ -f elf -dLINUX $< Have a nice day, Stepan Kasal _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Re: no rule to make asm targets
Hello, On Fri, Dec 08, 2006 at 01:05:14PM +0200, Jari Strand wrote: > I am sorry that I have to post again but I am still stuck with this > problem. Was it so that the problem should have been fixed after changing > the code to use the global target flags? I hope I have just done something > wrong now, but I need to know in order to figure what to try next. > > Do you have any suggestion for solving this issue, can I post other files? when I saw your last reply, I tried to look to your original post, but I was not able to identify any other problem which I could look at. So I suggest that you make a tarball that shows where you are right now, put it somewhere and post an URL. (Or you can attach it to your mail, if it is small.) It might help if you simplify the example, but it is not necessary. It is much more important that you make the example as self-contained as you can, with a clear description which commands to invoke, what is the result you observe and what is the expected result. List all dependencies on the installed packages, so that it is possible to reproduce your problem. And then hope that a reader of this list will find spare time to look at the issue. (Yes, there is no guarantee that the work you invest into formulating the question will pay off, unfortunately. :-( ) Sorry that we were not able to provide better help. (At least not yet.) Have a nice day, Stepan Kasal
Re: how to exclude the COPYING file
Hello, On Fri, Dec 08, 2006 at 11:00:09AM +0100, Presario Smith wrote: > AUTOMAKE_OPTIONS = foreign I'd prefer AM_INIT_AUTOMAKE([foreign]) in configure.ac, as this is a "global" option, affecting the whole project. But that's just a nit. Have a nice day, Stepan Kasal
