i tried to compile a recent windows version of streamin~/streamout~, but gave up after a few minutes. the cvs tarball seems to have cvs tags in the files, not usable at all.
also there seems to be no chance for me to compile this stuff with a free compiler for windows.
is it maybe possible to provide weekly or monthly binaries for windows?`i'm bored of downloading externals from different locations on the net, which are not recent versions.
On Thu, 27 Feb 2003, smoerk wrote:
i tried to compile a recent windows version of streamin~/streamout~, but gave up after a few minutes. the cvs tarball seems to have cvs tags in the files, not usable at all.
hi smoerk,
you are absolutely right, we should fix ASAP the build process for Windows.
But first, for those who want to try it, you have to install WinCVS. It is pretty useless to download the CVS tarball (which, you are right, can't be used for development).
So install CVS (there is documentation where to get it at pure-data.sf.net), or better go directly to
http://cvsgui.sourceforge.net/
and get WinCVS from there.
also there seems to be no chance for me to compile this stuff with a free compiler for windows.
is it maybe possible to provide weekly or monthly binaries for windows?`i'm bored of downloading externals from different locations on the net, which are not recent versions.
Yes, this would be great ! The problem we have currently is, that we do not have developers on windows that are willing to do this.
All of this is based on volunteers work. The advantage of the CVS is that we are in the position to collect all the work that is done. This work includes compiling externals and fixing the problems that accur when doing so.
So, again, this is a call for help. Is there anyone out there who is willing to do the compilation system for windows in the CVS ?
Guenter
guenter geiger wrote:
hi smoerk,
you are absolutely right, we should fix ASAP the build process for Windows.
But first, for those who want to try it, you have to install WinCVS. It is pretty useless to download the CVS tarball (which, you are right, can't be used for development).
but there is a link on pure-data.sf.net which says "If you absoluetly cannot use CVS, there are nightly CVS-tarballs of the whole project tree available (around 15 MB currently)".
maybe it would be wise to remove this, if there are no snapshots, which could be compiled.
also there seems to be no chance for me to compile this stuff with a free compiler for windows.
is it maybe possible to provide weekly or monthly binaries for windows?`i'm bored of downloading externals from different locations on the net, which are not recent versions.
Yes, this would be great ! The problem we have currently is, that we do not have developers on windows that are willing to do this.
All of this is based on volunteers work. The advantage of the CVS is that we are in the position to collect all the work that is done. This work includes compiling externals and fixing the problems that accur when doing so.
So, again, this is a call for help. Is there anyone out there who is willing to do the compilation system for windows in the CVS ?
what about cross-compiling from linux? i don't know if there is any chance to get it work... i cannot compile windows externals, because i cannot install a cracked version of MS VC++ on our university computers... ;-)
On Fri, 28 Feb 2003, smoerk wrote:
guenter geiger wrote:
hi smoerk,
you are absolutely right, we should fix ASAP the build process for Windows.
But first, for those who want to try it, you have to install WinCVS. It is pretty useless to download the CVS tarball (which, you are right, can't be used for development).
but there is a link on pure-data.sf.net which says "If you absoluetly cannot use CVS, there are nightly CVS-tarballs of the whole project tree available (around 15 MB currently)".
maybe it would be wise to remove this, if there are no snapshots, which could be compiled.
you are right, I thought I had this removed already. thanks for the pointer.
what about cross-compiling from linux? i don't know if there is any chance to get it work... i cannot compile windows externals, because i cannot install a cracked version of MS VC++ on our university computers... ;-)
:( I see. Best would be we to get them compiled with mingw or something then. Maybe I will find the time to do it ...
Greetings,
Guenter
Guenter, List,
So, again, this is a call for help. Is there anyone out there who is willing to do the compilation system for windows in the CVS ?
I can do this... we just need a functioning makefile for nmake for pd-CVS and each external I guess?
I haven't experimented with mingw but it would seem possible to use it, if required. I'll start out with something for vc++ and look towards mingw for the future.
If our goal is to use the SF build farm then I guess we should just work towards whatever is required/supported there.
Daniel
Daniel Heckenberg wrote:
If our goal is to use the SF build farm then I guess we should just work towards whatever is required/supported there.
they only have unix machines: linux, osx, solaris and freebsd. but there is mingw for cross-compiling. maybe it's possible to make windows binaries on sourceforge's compile farm.
On Friday, Feb 28, 2003, at 16:29 America/New_York, Daniel Heckenberg wrote:
Guenter, List,
So, again, this is a call for help. Is there anyone out there who is willing to do the compilation system for windows in the CVS ?
I can do this... we just need a functioning makefile for nmake for pd-CVS and each external I guess?
I don't know if you've looked into the 'build' directory in CVS, but many of the makefiles for externals have been condensed into a few key sections:
pd-externals (build/*/makefile): all externals without lib dependancies pd-flext (grill/flext/makefile): all flext related externals pd-osc (OSCx/*/makefile): all OSC related externals pd-zexy (zexy/src/makefile): zexy externals
I am just pointing this out, because you said we need a makefile for 'each external' and I wanted to save you some work.
.hc
Hans said:
I don't know if you've looked into the 'build' directory in CVS, but many of the makefiles for externals have been condensed into a few key sections:
...
I haven't been following the externals CVS so this info is handy, thanks.
It should be straightforward to get the Windows build system going then.
Daniel
On Mon, 3 Mar 2003, Daniel Heckenberg wrote:
Hans said:
I don't know if you've looked into the 'build' directory in CVS, but many of the makefiles for externals have been condensed into a few key sections:
...
I haven't been following the externals CVS so this info is handy, thanks.
It should be straightforward to get the Windows build system going then.
Yes, it should not be to hard. Zexy, flext and OSX should probably be compilable with their supplied Makefile. All other are built in build/platform directory.
The plan was to have a general build system for all externals, but I didn't want to mess around in the personal sub folders, so all externals that are compiled under the "build" tree are in build/src (actually they are some sort of links to the real externals).
I think for the future we should come up with some guidelines how to write externals, so that they fit into this framework.
Another goal is to do quality control on the externals, and just include those that meet the requirements of beeing reasonable bugfree.
This selection can be done with linking them to build/src.
We have to figure out how to use the bug-tracking on sourceforge too.
The goal is really to have this common place to share code, and to test externals on all platforms and to avoid duplicating efforts.
Great that you are doing this work, Daniel. I am happy if we have and nmake system for now, finally I would prefer mingw if this is doable.
Guenter
-
Daniel Heckenberg -
guenter geiger -
Hans-Christoph Steiner -
smoerk