I did did a fresh checkout of the zexy CVS today, and the README looks totally out-of-date (autoconf && ./configure ...) but there is not autoconf input files and no configure script.
So I went on a hunch and tried to use scons:
bbogart@insitu:~/pd-stuff/externals/zexy$ scons scons: *** No SConstruct file found. File "/usr/lib/scons/SCons/Script/__init__.py", line 870, in _main
I see a SConscript file in CVS, but no SConstruct...
Whats up? I see lots of posts about this in the archive (for all externals) but nothing about zexy specfically. I guess there is no Sconstruct file in .. relative to externals/zexy...
thanks.
b.
On any platform:
cd externals make -k install
("make -k" means continue on errors in case you don't have all the libs installed)
All of the externals, including zexy2.0, will be in build/extra once its done. Or it would not be too hard to make a zexy_install target. There already is smlib_install ext13_install cxc_install.
.hc
On Dec 3, 2005, at 11:53 AM, B. Bogart wrote:
I did did a fresh checkout of the zexy CVS today, and the README looks totally out-of-date (autoconf && ./configure ...) but there is not autoconf input files and no configure script.
So I went on a hunch and tried to use scons:
bbogart@insitu:~/pd-stuff/externals/zexy$ scons scons: *** No SConstruct file found. File "/usr/lib/scons/SCons/Script/__init__.py", line 870, in _main
I see a SConscript file in CVS, but no SConstruct...
Whats up? I see lots of posts about this in the archive (for all externals) but nothing about zexy specfically. I guess there is no Sconstruct file in .. relative to externals/zexy...
thanks.
b.
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
________________________________________________________________________ ____
Yes, but I DON'T want to build all the externals, only zexy2.
Why? * I don't have the bandwidth to suck down the whole externals CVS * I'm working on my "stable" installation and am only upgrading those components I need.
So how can I compile only zexy and nothing else?
Thanks for trying Hans. :)
b.
On any platform:
cd externals make -k install
("make -k" means continue on errors in case you don't have all the libs installed)
All of the externals, including zexy2.0, will be in build/extra once its done. Or it would not be too hard to make a zexy_install target. There already is smlib_install ext13_install cxc_install.
.hc
On Dec 3, 2005, at 11:53 AM, B. Bogart wrote:
I did did a fresh checkout of the zexy CVS today, and the README looks totally out-of-date (autoconf && ./configure ...) but there is not autoconf input files and no configure script.
So I went on a hunch and tried to use scons:
bbogart@insitu:~/pd-stuff/externals/zexy$ scons scons: *** No SConstruct file found. File "/usr/lib/scons/SCons/Script/__init__.py", line 870, in _main
I see a SConscript file in CVS, but no SConstruct...
Whats up? I see lots of posts about this in the archive (for all externals) but nothing about zexy specfically. I guess there is no Sconstruct file in .. relative to externals/zexy...
thanks.
b.
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
http://at.or.at/hans/
B. Bogart wrote:
I did did a fresh checkout of the zexy CVS today, and the README looks totally out-of-date (autoconf && ./configure ...) but there is not autoconf input files and no configure script.
there should be a configure.ac file in zexy/src
So I went on a hunch and tried to use scons:
bbogart@insitu:~/pd-stuff/externals/zexy$ scons scons: *** No SConstruct file found. File "/usr/lib/scons/SCons/Script/__init__.py", line 870, in _main
I see a SConscript file in CVS, but no SConstruct...
Whats up? I see lots of posts about this in the archive (for all externals) but nothing about zexy specfically. I guess there is no Sconstruct file in .. relative to externals/zexy...
cannot help you here.
fmg.asd.r IOhannes
Oh damn am I a dope...
I'll have to think hard about why I did not bother trying to compile from the src folder!! Its right there in the README I obviously even read!!!
Thanks for pointing out my idiocy.
FYI Johannes, for us (evil) skimmers, a little space between the heading and the instructions is really handy, or better yet bullents or numbers.
installation:: linux : change to directory src run: "autoconf" "./configure" "make" "make install"
becomes:
installation::
linux : 1. change to directory src (cd src) 2. autoconf 3. ./configure 4. make 5. make install
b.
B. Bogart wrote:
I did did a fresh checkout of the zexy CVS today, and the README looks totally out-of-date (autoconf && ./configure ...) but there is not autoconf input files and no configure script.
there should be a configure.ac file in zexy/src
So I went on a hunch and tried to use scons:
bbogart@insitu:~/pd-stuff/externals/zexy$ scons scons: *** No SConstruct file found. File "/usr/lib/scons/SCons/Script/__init__.py", line 870, in _main
I see a SConscript file in CVS, but no SConstruct...
Whats up? I see lots of posts about this in the archive (for all externals) but nothing about zexy specfically. I guess there is no Sconstruct file in .. relative to externals/zexy...
cannot help you here.
fmg.asd.r IOhannes
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev