Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
For information only, no reaction needed.
> Anfang der weitergeleiteten Nachricht:
>
> Von: "P.O. Jonsson" <oor...@jonases.se>
> Betreff: Aw: [Bsf4oorexx-devel] ooRexx installation from BSF versus
> standalone installation
> Datum: 5. April 2018 um 21:59:08 MESZ
> An: "Rony G. Flatscher" <rony.flatsc...@wu.ac.at>
>
> Dear Rony,
>
> All what you hint at below I do already I’m my scripts, there is no
> difference to install to
>
> /Library/Frameworks/ooRexx.framework/Versions/A
>
> Or
>
> /usr/local/ooRexx5.0.0
>
> Or whatever you want it to be. As I wrote earlier there is a 1:1 correlation
> between
>
> „My“ build „Bsf Build"
> /bin <-> /commands
> /include <-> /headers
> /lib <-> /libraries
> /share <-> /shared
>
> In the substructure /ooRexx5.0.0 or /A. The thing is that the names /bin,
> /lib etc come out of the cmake generator -G "Unix Makefiles“ and are generic
> Unix names that are probably used by all the other *nixes so I think they
> will be easier accepted.
>
> I guess that the ones you have comes out of the building of a „Framework“.
> Using „Packages“. I will try this out as well.
>
> These are the CMake Generators available for macOS
>
> The following generators are available on this platform:
> Unix Makefiles = Generates standard UNIX makefiles.
> Ninja = Generates build.ninja files.
> Xcode = Generate Xcode project files.
> CodeBlocks - Ninja = Generates CodeBlocks project files.
> CodeBlocks - Unix Makefiles = Generates CodeBlocks project files.
> CodeLite - Ninja = Generates CodeLite project files.
> CodeLite - Unix Makefiles = Generates CodeLite project files.
> Sublime Text 2 - Ninja = Generates Sublime Text 2 project files.
> Sublime Text 2 - Unix Makefiles
> = Generates Sublime Text 2 project files.
> Kate - Ninja = Generates Kate project files.
> Kate - Unix Makefiles = Generates Kate project files.
> Eclipse CDT4 - Ninja = Generates Eclipse CDT 4.0 project files.
> Eclipse CDT4 - Unix Makefiles= Generates Eclipse CDT 4.0 project files.
> KDevelop3 = Generates KDevelop 3 project files.
> KDevelop3 - Unix Makefiles = Generates KDevelop 3 project files.
>
> And I have not found one for building a Framework, my guess is that the
> „Packages“ takes care of it, and hence I must find a way to do the same using
> CPack (which means finding options for the CMakeLists.txt. Erich will not
> have anything else, unfortunately.
>
> I do all the symlinking you talk about, the symlinks are generated directly
> out of the Manifest file of the make install so they are 100% correct.
>
> Please do not spend any more time on these matters, the information you have
> given is sufficient. I understand how your build is done and I will go after
> a CPack solution soon. I have cleaned a Mac and installed High Sierra so as
> to have a pristine start, this brought some surprises, I will write about it
> in another mail.
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se <mailto:oor...@jonases.se>
>
>
>
>
>> Am 05.04.2018 um 19:14 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at
>> <mailto:rony.flatsc...@wu.ac.at>>:
>>
>> On 04.04.2018 17:39, P.O. Jonsson wrote:
>>> Re "We should stick to the standard by using one of the CPack package
>>> generators."
>>>
>>> That’s what I tried for about a week without succeeding :-(
>>>
>>> I agree that this is the ultimate goal, once you get it right I am sure it
>>> looks trivial but this is all new waters for me.
>> Maybe it is possible to define at least a
>> "/Library/Frameworks/ooRexx.framework/Versions/ooRexx.X.Y.Z-SVNr" with the
>> Apple framework bundle subdirectories
>> "Commands"
>> "Headers"
>> "Libraries"
>> "Shared"
>> as the BSF4ooRexx installation does (it currently uses as ooRexx version
>> name the simple name "A" which stems from some Apple documentation).
>>
>> Then do a symbolic link of "Versions/Current" to
>> "Versions/ooRexx.X.Y.Z-SVNr" which would make your installed version of
>> ooRexx the current version to use.
>>
>> Note, that in "/Library/Frameworks/ooRexx.framework" the following
>> subdirectories are actually symbolic links to "../Versions/Current":
>>
>> "Commands -> Versions/Current/Commands"
>> "Headers -> Versions/Current/Headers"
>> "Libraries -> Versions/Current/Libraries"
>> "Shared -> Versions/Current/Shared"
>> Note that in "/usr/local/bin", "/usr/local/include", "/usr/local/lib", and
>> "/usr/local/share/man/man1" etc. the symbolic links go to the subdirectories
>> of "/Library/Frameworks/ooRexx.framework", namely:
>>
>> "-> /Library/Frameworks/ooRexx.framework/Commands/..."
>> "-> /Library/Frameworks/ooRexx.framework/Headers/..."
>> "-> /Library/Frameworks/ooRexx.framework/Libraries/..."
>> "-> /Library/Frameworks/ooRexx.framework/Shared/..."
>> This entire setup and system may look complicated at first, however it
>> easies installation and maintenance of multiple versions of a software.
>> Switching from one version to another is then simply the creation of a
>> symbolic link from ".../Versions/ooRexx.X.Y.Z-SVNr" to
>> ".../Versions/Current".
>>
>> ---
>>
>> One more important thing: at least on Linux it is important to supply
>> additional links to the libraries that include the major ooRexx version
>> numbers that the ooRexx libraries are ABI compatible to allow programs
>> linked to earlier versions of ooRexx to still be able to link and run with
>> ooRexx 5. On Linux this means to have e.g. (for the rexx library):
>> /usr/lib/librexx.so -> {wherever}librexx.so.5.0.0
>> /usr/lib/librexx.so.2 -> librexx.so
>> /usr/lib/librexx.so.3 -> librexx.so
>> /usr/lib/librexx.so.4 -> librexx.so
>> The same might be needed for MacOSX according to
>> <https://docstore.mik.ua/orelly/unix3/mac/ch05_04.htm>
>> <https://docstore.mik.ua/orelly/unix3/mac/ch05_04.htm>, which for the above
>> example might need to have something like:
>> /usr/local/lib/librexx.dylib ->
>> /Library/Frameworkds/ooRexx.framework/Libraries/librexx.5.0.0.dylib
>> /usr/local/lib/librexx.2.dylib -> librexx.dylib
>> /usr/local/lib/librexx.3.dylib -> librexx.dylib
>> /usr/local/lib/librexx.4.dylib -> librexx.dylib
>> /usr/local/lib/librexx.5.dylib -> librexx.dylib
>> or the like.
>>
>> HTH
>>
>> ---rony
>>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
