Are you checking for those files after a build and a make install, or are you checking for an install from a built installer (eg, rpm, deb, windows installer)? Those files get built and I'm guessing that a make install probably copies them. They are not specified for inclusion in the package builds in CMakeLists.txt. If your installer is just using the results of make install to build the package, then it is not using the install information built by CMakeLists.txt. CMakeLists.txt uses a series of install() statements to identify which build artifacts are to be installed and where they should be installed. This creates a file in the cmake directory called cmake_install.cmake which is a cmake script that identifies what files are to be installed (and what component they are part of). These scripts are used for the various CPack options and also by the Windows NSIS installer. The compiled samples like callrxnt are not included in the installation definitions.
Rick Rick On Mon, Jul 19, 2021 at 11:14 AM P.O. Jonsson <oor...@jonases.se> wrote: > Ok, so I checked rev 12280 on some Linux installations (Raspberry Pi, > Debian, Linux Mint, Fedora, CentOS) and they all show the same 2 CallRexx > and 3 Libwpipe files in the installed /bin directory, so it is not just > macOS/Darwin thingy, it is a generic fault (if it is a fault) for the > *nixes. > > I could not find oorexx-config in ANY installation so I guess this is a > local file on Rony´s computer, maybe from the „fat binary“ exercise? It is > not present in any of the installations I looked at. None. > > Windows is entirely different from the rest of the installations and there > are some Callrxnt.exe etc files in the installed ooRexx (I only looked at > the 64-bit version) but I must assume that they are intentionally there > since the Windows installer is *properly* using CMakelists.txt, right? > > Hälsningar/Regards/Grüsse, > P.O. Jonsson > oor...@jonases.se > > > > Am 16.07.2021 um 18:04 schrieb Rick McGuire <object.r...@gmail.com>: > > btw, if you were properly using the information from CMake.txt to build > the .dmg, you would not be having this problem, since all of the install() > statements identify which elements of the build should go where. That > information is used by all of the other installer types (including the > Windows one, which is done without CMake builtin CPack support). > > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel >
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
