In the current 'externals' build system, all of the help files are checked into externals/build/doc. It seems to me that this means that we have two copies of each file to maintain: the original and the one in externals/build/doc. I am writing a section in the makefile for darwin to copy these files from the source. I would like to put this in all of the makefiles (darwin, irix, linux, and win) unless anyone has any objections. Then I'll delete externals/build/doc from the CVS since it will then be generated by the makefile.
.hc
On Sunday 14 September 2003 21:56, Hans-Christoph Steiner wrote:
In the current 'externals' build system, all of the help files are checked into externals/build/doc. It seems to me that this means that we have two copies of each file to maintain: the original and the one in externals/build/doc. I am writing a section in the makefile for darwin to copy these files from the source. I would like to put this in all of the makefiles (darwin, irix, linux, and win) unless anyone has any objections. Then I'll delete externals/build/doc from the CVS since it will then be generated by the makefile.
.hc
Wouldn't it make even more sense for "make install" to copy these files to somewhere where PD can by default see them?
I didn't even know that there was a ~/externals/build/doc directory until you mentioned in just now.
I guess somewhere in some readme there's a suggestion to add this to PD's help search list, huh?
Larry
On Mon, 15 Sep 2003, Larry Troxler wrote:
On Sunday 14 September 2003 21:56, Hans-Christoph Steiner wrote:
In the current 'externals' build system, all of the help files are checked into externals/build/doc. It seems to me that this means that we have two copies of each file to maintain: the original and the one in externals/build/doc. I am writing a section in the makefile for darwin to copy these files from the source. I would like to put this in all of the makefiles (darwin, irix, linux, and win) unless anyone has any objections. Then I'll delete externals/build/doc from the CVS since it will then be generated by the makefile.
.hc
Wouldn't it make even more sense for "make install" to copy these files to somewhere where PD can by default see them?
I didn't even know that there was a ~/externals/build/doc directory until you mentioned in just now.
I guess somewhere in some readme there's a suggestion to add this to PD's help search list, huh?
Hi,
This is a CVS organization issue and has nothing to do with installing help files.
I copied the help files into the folder because they had to be renamed for version 0.37 (with the help- prefix).
I think copying them automaticaly with the makefile is a good idea.
Guenter
i tried running pd 0.37 on a stripped down linux system yesterday, and it crashed when the HOME environment variable was not set. getenv("HOME") returns NULL in s_path.c, function int sys_rcfile(void), which will cause the line
strncat(fname, getenv("HOME"), MAXPDSTRING-10);
(number 308) to die.
sorry if this is already fixed, i'm running 0.37-test8
tom
Thanks... I'll fix it. I presume just "." is the most natural fallback when there's no $HOME...
cheers Miller
On Mon, Sep 15, 2003 at 12:19:10PM +0200, Tom Schouten wrote:
i tried running pd 0.37 on a stripped down linux system yesterday, and it crashed when the HOME environment variable was not set. getenv("HOME") returns NULL in s_path.c, function int sys_rcfile(void), which will cause the line
strncat(fname, getenv("HOME"), MAXPDSTRING-10);
(number 308) to die.
sorry if this is already fixed, i'm running 0.37-test8
tom
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev
hello,
i'm running hp-ux 11i (HP visualize B1000 workstation) anybody has any experience installing pd on such ? tips to compile it ?
thnx, pieter.