build system for clips
15 views
Skip to first unread message
squi...@gmail.com
Jun 14, 2007, 4:22:09 PM6/14/07
to CLIPSESG
Why does clips not have a standard build system? For example, with the
clips source code package being overwritten every time a new release
is made, it makes it impossible to stably tell some source-based
distributions where to get certain versions of clips. For the *nix
users, could we please have an automake-based distribution?
I have attached an automake build system with instructions at
http://bugs.gentoo.org/show_bug.cgi?id=49964 and if anyone would like
help or more information on using it, please shoot me an email.
-Jon Hood
clips source code package being overwritten every time a new release
is made, it makes it impossible to stably tell some source-based
distributions where to get certain versions of clips. For the *nix
users, could we please have an automake-based distribution?
I have attached an automake build system with instructions at
http://bugs.gentoo.org/show_bug.cgi?id=49964 and if anyone would like
help or more information on using it, please shoot me an email.
-Jon Hood
CLIPS Support
Jun 14, 2007, 9:03:06 PM6/14/07
to CLIPSESG
I'll put *nix automake-based distributions on the list of things to
learn about.
learn about.
On Jun 14, 3:22 pm, "squink...@gmail.com" <squink...@gmail.com> wrote:
> Why does clips not have a standard build system? For example, with the
> clips source code package being overwritten every time a new release
> is made, it makes it impossible to stably tell some source-based
> distributions where to get certain versions of clips. For the *nix
> users, could we please have an automake-based distribution?
> I have attached an automake build system with instructions athttp://bugs.gentoo.org/show_bug.cgi?id=49964and if anyone would like
Rick Vinyard
Jun 21, 2007, 1:11:02 AM6/21/07
to CLIP...@googlegroups.com
If you're interested, here is the patch I created for the Fedora CLIPS package: http://miskatonic.cs.nmsu.edu/pub/clips-6.24-linux.patch
It requires a slight restructuring of the CLIPS source directories, namely the following:
mv x-prjct/xinterface clipssrc/
mv x-prjct/color clipssrc/
mv clipssrc/clipssrc clipssrc/clips
The first two directory moves are necessary since I structured it to build the X interface as well. The last is to provide an include hierarchy that can be installed in /usr/include/clips.
The included autotools files will create CLIPS libtool dynamic and static libraries, the xclips interface and the color utility (renamed to xclips-color). It also includes a pkgconfig specification file, which (IMHO) makes using the CLIPS dynamic library quite a bit easier.
In particular, I wanted CLIPS as a dynamic library that clipsmm could be built against.
It requires a slight restructuring of the CLIPS source directories, namely the following:
mv x-prjct/xinterface clipssrc/
mv x-prjct/color clipssrc/
mv clipssrc/clipssrc clipssrc/clips
The first two directory moves are necessary since I structured it to build the X interface as well. The last is to provide an include hierarchy that can be installed in /usr/include/clips.
The included autotools files will create CLIPS libtool dynamic and static libraries, the xclips interface and the color utility (renamed to xclips-color). It also includes a pkgconfig specification file, which (IMHO) makes using the CLIPS dynamic library quite a bit easier.
In particular, I wanted CLIPS as a dynamic library that clipsmm could be built against.
Reply all
Reply to author
Forward
0 new messages