Re: [PD-dev] pd-extended build logs
Hallo! The Windows scripts might not send emails, since it's a pain to do that on Windows. Feel free to get that working. [...] Get it working on any machine, then check it into CVS. That's what the auto-builds use. Ideally, it would use only software in Cygwin or MinGW. So someone needs to figure out how to send emails from a script on a Windows machine. Can you point me to the place in cvs where this is done ? - I cannot find it ... LG Georg ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] pd-extended build logs
On 28/01/2007, at 18.00, Georg Holzmann wrote:
Hallo!
The Windows scripts might not send emails, since it's a pain
to do that on Windows. Feel free to get that working.
[...]
Get it working on any machine, then check it into CVS. That's
what the auto-builds use. Ideally, it would use only software
in Cygwin or MinGW. So someone needs to figure out how to send
emails
from a script on a Windows machine.
Can you point me to the place in cvs where this is done ? - I
cannot find it ...
I think you are to look in http://pure-data.cvs.sourceforge.net/pure-
data/scripts/auto-build/
In other words:
$ pwd
/path/to/cvsroot/scripts/auto-build
$ grep -iG '\(mail\|pd-cvs\)' *
auto-build-common:# recipient of any emails set from the scripts
auto-build-common:[EMAIL PROTECTED]
pd-devel-auto-builder.sh:# if the below word prints, the status
report email is not sent
run-automated-builder:tail -20 ${LOGFILE} | mail -s $
{SUBJECT} ${RECIPIENT}
best, steffen
___
PD-dev mailing list
PD-dev@iem.at
http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] pd-extended build logs
Hallo! Can you point me to the place in cvs where this is done ? - I cannot find it ... I think you are to look in http://pure-data.cvs.sourceforge.net/pure-data/scripts/auto-build/ thanks - I saw it now ... Do the autobuilds run in a specific order ? Then we could e.g. simply download the windows log file during the linux-autobuild and mail it from the linux-machine to pd-cvs ... I will try it when autobuild.puredata is up again. LG Georg ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] pd-extended build logs
Hallo! And one more question: All the new externals I added in the last weeks are not in the windows installers - the I saw that there is also no Pd-0.40 for windows ... Are there any special things to do to get Pd-0.40-extended for windows ? Get ./configure make working with Windows/MinGW. I had something almost working in the past, it's not too hard to do. I just am rarely near a Windows box. Sorry, but I don't understand your answer. I only ask why Pd-extended is not build on windows - why is it a problem with 0.40 if 0.39 works ? LG Georg ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] pd-extended build logs
Hallo! The Windows scripts might not send emails, since it's a pain to do that on Windows. Feel free to get that working. How should I get this working ? - I would have to log me into the windows machine ... LG Georg ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] pd-extended build logs
On Jan 27, 2007, at 5:56 AM, Georg Holzmann wrote: Hallo! The Windows scripts might not send emails, since it's a pain to do that on Windows. Feel free to get that working. How should I get this working ? - I would have to log me into the windows machine ... Get it working on any machine, then check it into CVS. That's what the auto-builds use. Ideally, it would use only software in Cygwin or MinGW. So someone needs to figure out how to send emails from a script on a Windows machine. .hc LG Georg As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously. - Benjamin Franklin ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] pd-extended build logs
On Sat Jan 27, 2007 at 05:06:06PM -0500, Hans-Christoph Steiner wrote: On Jan 27, 2007, at 5:56 AM, Georg Holzmann wrote: Hallo! The Windows scripts might not send emails, since it's a pain to do that on Windows. Feel free to get that working. How should I get this working ? - I would have to log me into the windows machine ... Get it working on any machine, then check it into CVS. That's what the auto-builds use. Ideally, it would use only software in Cygwin or MinGW. So someone needs to figure out how to send emails from a script on a Windows machine. or you could just commit the build log to a file and use CVS's equivalenet of .git/hooks/post-commit to send it from the CVS server.. which is more likely to be able to get mails through the -cvs list address anyways .hc LG Georg As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously. - Benjamin Franklin ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] pd-extended build logs
On Jan 27, 2007, at 7:14 PM, carmen wrote: On Sat Jan 27, 2007 at 05:06:06PM -0500, Hans-Christoph Steiner wrote: On Jan 27, 2007, at 5:56 AM, Georg Holzmann wrote: Hallo! The Windows scripts might not send emails, since it's a pain to do that on Windows. Feel free to get that working. How should I get this working ? - I would have to log me into the windows machine ... Get it working on any machine, then check it into CVS. That's what the auto-builds use. Ideally, it would use only software in Cygwin or MinGW. So someone needs to figure out how to send emails from a script on a Windows machine. or you could just commit the build log to a file and use CVS's equivalenet of .git/hooks/post-commit to send it from the CVS server.. which is more likely to be able to get mails through the - cvs list address anyways On all the other platforms, the script sends the email, so it makes sense to do that on Windows too. It sends a truncated version, so you only get the error. The build logs are megabytes of text, so I'd really rather not that they get sent to pd-cvs or get checked into CVS. .hc .hc LG Georg - --- As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously. - Benjamin Franklin ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev Mistrust authority - promote decentralization. - the hacker ethic ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] pd-extended build logs
On Jan 25, 2007, at 1:15 PM, Frank Barknecht wrote: Hallo, Georg Holzmann hat gesagt: // Georg Holzmann wrote: The script only sends the email if the build fails. The complete logs are on the website if you want to see them. e.g. the log from today says: (see [1]) And one more question: All the new externals I added in the last weeks are not in the windows installers For whatever reason 0.40 for Windows isn't built ATM. And to get your externals into the 0.39 builds, they need to be tagged in CVS, because this build is not built from HEAD, but from branch-v0-39-2-extended or so. That is true, but please don't just start adding anything to that branch. It is almost at release candidate, which is total code freeze, so its a really bad time to add a bunch of new code. Only if it's trivial or essential to this release. I want to get these releases stable, that this is one of the steps necessary to making stable releases. .hc Ciao -- Frank Barknecht _ __footils.org_ __goto10.org__ ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev News is what people want to keep hidden and everything else is publicity. - Bill Moyers ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] pd-extended build logs
On Jan 24, 2007, at 3:16 AM, Georg Holzmann wrote: Hallo! The script only sends the email if the build fails. The complete logs are on the website if you want to see them. yes, but e.g. the windows builds fail too (I looked into the log file on the website) and weren't send to pd-cvs list ... LG Georg The Windows scripts might not send emails, since it's a pain to do that on Windows. Feel free to get that working. .hc There is no way to peace, peace is the way. -A.J. Muste ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] pd-extended build logs
Hallo! The script only sends the email if the build fails. The complete logs are on the website if you want to see them. e.g. the log from today says: (see [1]) And one more question: All the new externals I added in the last weeks are not in the windows installers - the I saw that there is also no Pd-0.40 for windows ... Are there any special things to do to get Pd-0.40-extended for windows ? LG Georg [1]: --- strip --strip-unneeded -R .note -R .comment /home/pd/auto-build/pd-extended/externals/hcs/version.dll rm -f -- /home/pd/auto-build/pd-extended/externals/hcs/version.o gcc -DPD -O2 -mcpu=i586 -mtune=pentium3 -I/home/pd/auto-build/pd-extended/pd/src -Wall -W -ggdb -mms-bitfields -DMSW -DNT -D'O_NONBLOCK=1' -D'srand48(n)=srand((n))' -D'drand48()=((double)rand()/RAND_MAX)' -D'bzero(p,n)=memset(p,0,n)' -o /home/pd/auto-build/pd-extended/externals/io/hidio/hidio_windows.o -c /home/pd/auto-build/pd-extended/externals/io/hidio/hidio_windows.c gcc -DPD -O2 -mcpu=i586 -mtune=pentium3 -I/home/pd/auto-build/pd-extended/pd/src -Wall -W -ggdb -mms-bitfields -DMSW -DNT -D'O_NONBLOCK=1' -D'srand48(n)=srand((n))' -D'drand48()=((double)rand()/RAND_MAX)' -D'bzero(p,n)=memset(p,0,n)' -o /home/pd/auto-build/pd-extended/externals/io/hidio/hidio_types.o -c /home/pd/auto-build/pd-extended/externals/io/hidio/hidio_types.c gcc -DPD -O2 -mcpu=i586 -mtune=pentium3 -I/home/pd/auto-build/pd-extended/pd/src -Wall -W -ggdb -mms-bitfields -DMSW -DNT -D'O_NONBLOCK=1' -D'srand48(n)=srand((n))' -D'drand48()=((double)rand()/RAND_MAX)' -D'bzero(p,n)=memset(p,0,n)' -o /home/pd/auto-build/pd-extended/externals/io/hidio/hidio.o -c /home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:507: warning: unused parameter 'x' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:528: warning: unused parameter 's' gcc -shared -o /home/pd/auto-build/pd-extended/externals/io/hidio/hidio.dll \ /home/pd/auto-build/pd-extended/externals/io/hidio/hidio_windows.o /home/pd/auto-build/pd-extended/externals/io/hidio/hidio_types.o /home/pd/auto-build/pd-extended/externals/io/hidio/hidio.o -lm -L/home/pd/auto-build/pd-extended/pd/bin -L/home/pd/auto-build/pd-extended/pd/obj -lpd -lwsock32 -lpthreadGC2 -lkernel32 -luser32 -lgdi32 -lregex -lhid -lsetupapi C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.o: In function `get_device_number_from_arguments':C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:242: undefined reference to `get_device_number_from_usage' :C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:281: undefined reference to `get_device_number_by_id' :C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:271: undefined reference to `get_device_number_from_usage' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.o: In function `hidio_close':C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:381: undefined reference to `hidio_close_device' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.o: In function `hidio_open':C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:413: undefined reference to `hidio_open_device' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.o: In function `hidio_tick':C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:455: undefined reference to `hidio_get_events' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.o: In function `hidio_info':C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:488: undefined reference to `hidio_platform_specific_info' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.o: In function `hidio_setup':C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:584: undefined reference to `hidio_build_device_list' :C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:586: undefined reference to `hidio_print' :C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:592: undefined reference to `hidio_ff_autocenter' :C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:594: undefined reference to `hidio_ff_gain' :C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:595: undefined reference to `hidio_ff_motors' :C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:596: undefined reference to `hidio_ff_continue' :C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:597: undefined reference to `hidio_ff_pause' :C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:598: undefined reference to `hidio_ff_reset' :C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:599: undefined reference to `hidio_ff_stopall'
Re: [PD-dev] pd-extended build logs
Hallo, Georg Holzmann hat gesagt: // Georg Holzmann wrote: The script only sends the email if the build fails. The complete logs are on the website if you want to see them. e.g. the log from today says: (see [1]) And one more question: All the new externals I added in the last weeks are not in the windows installers For whatever reason 0.40 for Windows isn't built ATM. And to get your externals into the 0.39 builds, they need to be tagged in CVS, because this build is not built from HEAD, but from branch-v0-39-2-extended or so. Ciao -- Frank Barknecht _ __footils.org_ __goto10.org__ ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
