On 09.02.2011 16:54, CVBruce wrote:
> Some of the scripts to create a distributable package for ooRexx are located
> in platform/unix/macos. The problem I ran into was that between 4.0.1 and
> 4.1 the install strategy for ooRexx was completely changed. There are also
> parts of the creation process that take part in the make install portion of
> the Makefile. I wish I hadn't done that but at the time I couldn't think of
> a different way of doing it.
>
Skimming over Postflight.in:
* there are entries of non-existent dylibs to create links for, e.g.:
o $PREFIX/lib/ooRexx/librexx
o $PREFIX/lib/ooRexx/librexxapi
o $PREFIX/lib/ooRexx/librexxutil
o $PREFIX/lib/ooRexx/librxmath
o $PREFIX/lib/ooRexx/librxregexp
o $PREFIX/lib/ooRexx/librxsock
* probably the following file should be linked to /usr/bin
o share/ooRexx/rexxtry.rex
not sure about:
o share/ooRexx/rexx.csh
o share/ooRexx/rexx.sh
* there are new, unreferenced libraries, files, which need to be
linked now as well, namely:
o lib/libhostemu.*
o lib/librxunisys.*
o bin/csvStream.cls
o bin/mime.cls
o bin/smtp.cls
o bin/streamsocket.cls
* didn't see "bin/rxapid" in the created ooRexx gz-package, which
gets linked to /usr/bin
Probably other files that may have been added since the creation of the
scripts, not listed here.
(Postflight.in.would probably need appropriate adjustments.)
---rony
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
