Hallo!
In the last days only mac build logs were sent to the pd-cvs mailinglist. I'm just curios why not the others ?
LG Georg
The script only sends the email if the build fails. The complete logs are on the website if you want to see them.
.hc
On Jan 23, 2007, at 5:34 AM, Georg Holzmann wrote:
Hallo!
In the last days only mac build logs were sent to the pd-cvs mailinglist. I'm just curios why not the others ?
LG Georg
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
------------------------------------------------------------------------
If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of everyone, and the receiver cannot dispossess himself of it. - Thomas Jefferson
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
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
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
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
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
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:RECIPIENT=pd-cvs@iem.at 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
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
On Jan 28, 2007, at 2:10 PM, Georg Holzmann wrote:
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 ...
FYI: All the scripts used for the auto-builds are there.
Do the autobuilds run in a specific order ?
Check scripts/auto-build/run-automated-builder for what it run on each machine. As for which machine runs when, they use the default cron.daily times for that platform, usually somewhere between 3am and 6:30am EST. debian-stable-i386 also serves as the CVS, rsync, and web server, so it runs its auto-build jobs at around 1:30am EST.
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 ...
That sounds like a kludge which will bite us in the end. I think this should be done "the right way", using something in Cygwin or Mingw. That will be the least amount of work in the long run. Each computer needs to be self-contained or it rapidly becomes unmaintainable.
.hc
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
------------------------------------------------------------------------
There is no way to peace, peace is the way. -A.J. Muste
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' :C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:601: undefined reference to `hidio_ff_fftest' :C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:602: undefined reference to `hidio_ff_print' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.o: In function `hidio_free':C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.c:524: undefined reference to `hidio_platform_specific_free' collect2: ld returned 1 exit status make[2]: *** [/home/pd/auto-build/pd-extended/externals/io/hidio/hidio.dll] Error 1 make[2]: Leaving directory `/home/pd/auto-build/pd-extended/externals' make[1]: *** [externals_install] Error 2 make[1]: Leaving directory `/home/pd/auto-build/pd-extended/packages' make: *** [prebuilt_install] Error 2 upload specs win32_inno Output exe Uploading /home/pd/auto-build/pd-extended/packages/win32_inno/Output/Pd*.exe ls: /home/pd/auto-build/pd-extended/packages/win32_inno/Output/Pd*.exe: No such file or directory -------------------------------
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
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
On Jan 25, 2007, at 1:01 PM, 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.
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 ?
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.
.hc
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' :C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/ hidio.c:601: undefined reference to `hidio_ff_fftest' :C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/ hidio.c:602: undefined reference to `hidio_ff_print' C:/msys/1.0/home/pd/auto-build/pd-extended/externals/io/hidio/ hidio.o: In function `hidio_free':C:/msys/1.0/home/pd/auto-build/pd- extended/externals/io/hidio/hidio.c:524: undefined reference to `hidio_platform_specific_free' collect2: ld returned 1 exit status make[2]: *** [/home/pd/auto-build/pd-extended/externals/io/hidio/ hidio.dll] Error 1 make[2]: Leaving directory `/home/pd/auto-build/pd-extended/externals' make[1]: *** [externals_install] Error 2 make[1]: Leaving directory `/home/pd/auto-build/pd-extended/packages' make: *** [prebuilt_install] Error 2 upload specs win32_inno Output exe Uploading /home/pd/auto-build/pd-extended/packages/win32_inno/ Output/Pd*.exe ls: /home/pd/auto-build/pd-extended/packages/win32_inno/Output/ Pd*.exe: No such file or directory
------------------------------------------------------------------------
Access to computers should be unlimited and total. - the hacker ethic
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
On Jan 27, 2007, at 5:54 AM, Georg Holzmann wrote:
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 ?
Because I am currently using an really ugly kludge that should be removed. It is not too hard to get the ./configure && make stuff working on Windows, and it has a lot of advantages, so I am not supporting the ugly kludge anymore. Plus, if the ./configure && make stuff works on Windows, I think it'll be easier to cross-compile for Windows from other free platforms, like Debian.
.hc
LG Georg
------------------------------------------------------------------------
Looking at things from a more basic level, you can come up with a more direct solution... It may sound small in theory, but it in practice, it can change entire economies. - Amy Smith
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
Because I am currently using an really ugly kludge that should be removed. It is not too hard to get the ./configure && make stuff working on Windows, and it has a lot of advantages, so I am not supporting the ugly kludge anymore. Plus, if the ./configure && make stuff works on Windows, I think it'll be easier to cross-compile for Windows from other free platforms, like Debian.
Hm, at first I wanted to suggest trying to build the externals at least for Windows as well, even without Pd which would be useful to spot platform specific bugs early on. But then I remembered, that some kind of pd.lib is needed on Windows to build externals, isn't it? And this probably won't build, if Pd won't build. Hm++.
Ciao
Hallo!
Because I am currently using an really ugly kludge that should be removed. It is not too hard to get the ./configure && make stuff working on Windows, and it has a lot of advantages, so I am not supporting the ugly kludge anymore. Plus, if the ./configure && make stuff works on Windows, I think it'll be easier to cross-compile for Windows from other free platforms, like Debian.
Hm ... so this means that ATM Pd-Extended is not supported for windows at all?
I'm sorry, I have no windows machine here - but maybe we can just reactivate the "ugly kludge", so that we have at least something ?
Maybe you can point me to some places in cvs where this is done - then I can try a little bit ...
LG Georg
On Jan 28, 2007, at 12:13 PM, Georg Holzmann wrote:
Hallo!
Because I am currently using an really ugly kludge that should be removed. It is not too hard to get the ./configure && make stuff working on Windows, and it has a lot of advantages, so I am not supporting the ugly kludge anymore. Plus, if the ./configure && make stuff works on Windows, I think it'll be easier to cross- compile for Windows from other free platforms, like Debian.
Hm ... so this means that ATM Pd-Extended is not supported for windows at all?
I'm sorry, I have no windows machine here - but maybe we can just reactivate the "ugly kludge", so that we have at least something ?
Maybe you can point me to some places in cvs where this is done - then I can try a little bit ...
The ugly kludge is used in the test/RC versions(branch-v0-39-2- extended), just not in 0.40.2 yet (HEAD/MAIN of Pd-extended). I'm not going to port the kludge, it was a mistake to port it from 0.38.4 to 0.39.2, so I am not going to repeat that mistake.
.hc
LG Georg
------------------------------------------------------------------------
¡El pueblo unido jamás será vencido!
Hallo!
The ugly kludge is used in the test/RC versions(branch-v0-39-2-extended), just not in 0.40.2 yet (HEAD/MAIN of Pd-extended). I'm not going to port the kludge, it was a mistake to port it from 0.38.4 to 0.39.2, so I am not going to repeat that mistake.
Okay ... Have you plans to get it working with configure+etc for windows in the next time ?
(I don't want to stress - I am only interessted in the plan for the future ... :)
Thanks, LG Georg
On Jan 29, 2007, at 12:23 PM, Georg Holzmann wrote:
Hallo!
The ugly kludge is used in the test/RC versions(branch-v0-39-2- extended), just not in 0.40.2 yet (HEAD/MAIN of Pd-extended). I'm not going to port the kludge, it was a mistake to port it from 0.38.4 to 0.39.2, so I am not going to repeat that mistake.
Okay ... Have you plans to get it working with configure+etc for windows in the next time ?
(I don't want to stress - I am only interessted in the plan for the future ... :)
I have no plans to do that work. If no one else does it by the next release cycle, then I'll probably end up working on Windows again, even though I never use Windows... but I really rather not.
.hc
Thanks, LG Georg
------------------------------------------------------------------------
There is no way to peace, peace is the way. -A.J. Muste
-
carmen -
Frank Barknecht -
Georg Holzmann -
Hans-Christoph Steiner -
Steffen