Re: [Oorexx-devel] Cmake deprecation warning

Hi P.O., this is just a deprecation warning. As soon as we use cmake_policy(VERSION ..) we run deprecated – that's to be expected. My Ubuntu 16 Jenkins client runs CMake 3.5.1. I wouldn't bump cmake minimum until absolutely required. ___ Oorexx-devel mai

Re: [Oorexx-devel] CMake

> Am 07.03.2021 um 18:16 schrieb Rick McGuire : > > I found the old thread from 2018 which discussed the last time we updated the > required version number. I think leaving the other CMake.txt files as 2.6 was > just an oversight and they should also have been updated to 2.8 at that time. > Ho

Re: [Oorexx-devel] CMake

@Enrico: Can you enlighten us on the purpose of cmake_policy? Should it stay or should it go? @Rick: I found CMake-build-readme.txt where CMake is discussed - are there more places? I guess the WIKI needs some updating as well but I have no access to that. Hälsningar/Regards/Grüsse, P.O. Jons

Re: [Oorexx-devel] CMake

I suspect it should. Also note that there are some notes about CMake versions in the build instructions that will also need updating. Rick On Sun, Mar 7, 2021 at 12:35 PM P.O. Jonsson wrote: > What about this line, should I include it in all places as well? > > cmake_policy(VERSION 2.8...3.3) >

Re: [Oorexx-devel] CMake

What about this line, should I include it in all places as well? cmake_policy(VERSION 2.8...3.3) Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 07.03.2021 um 18:24 schrieb P.O. Jonsson : > > > >> Am 07.03.2021 um 18:16 schrieb Rick McGuire > >:

Re: [Oorexx-devel] CMake

> Am 07.03.2021 um 18:16 schrieb Rick McGuire : > > I found the old thread from 2018 which discussed the last time we updated the > required version number. I think leaving the other CMake.txt files as 2.6 was > just an oversight and they should also have been updated to 2.8 at that time. > H

Re: [Oorexx-devel] CMake

I found the old thread from 2018 which discussed the last time we updated the required version number. I think leaving the other CMake.txt files as 2.6 was just an oversight and they should also have been updated to 2.8 at that time. However, I would not be at all opposed to bumping everything to 3

Re: [Oorexx-devel] CMake

I'm currently running 3.11.4 for my Windows build, I can easily upgrade to a new version if needed. The last time I bumped the version level higher, there was some objections because of some other platforms. I don't recall what the specific objections were. Rick On Sun, Mar 7, 2021 at 11:52 AM P.

Re: [Oorexx-devel] CMake

I think there is a general agreement that requiring 3.12 for macOS is ok (Jenkins macOS slave is running 3.13.2). Now I am more interested to hear what the Windows users have to say - is there any reason NOT to go from 2.6 to 2.8 as the minimum? I would prefer to have the same settings in all C

Re: [Oorexx-devel] CMake

Whatever. My point was the ready availability of Cmake recent versions for Mac. When I first built ooRexx V5, Rick told me I needed Version 3 of Cmake, which was readily available. Sent by Magic! > On Mar 7, 2021, at 7:16 AM, Enrico Sorichetti via Oorexx-devel > wrote: > > IMO the best way

Re: [Oorexx-devel] CMake

IMO the best way to install cmake on APPLE is to use the drag and drop dmg Available in the download section at cmake.org You get a first hand build , it allows to keep updated with minimal effort It installs into /Applications and it can create a symlink into /usr/local Test

Re: [Oorexx-devel] CMake

Apple is notorious for updating packages based on their own needs, which is why I use MacPorts. The current MacPorts version of CMake is 3.19.6. Fink is 3.19.1, and Homebrew is also 3.19.6. I would be in favor of raising the required Cmake level. Sent by Magic! > On Mar 7, 2021, at 5:50 AM, Mic

Re: [Oorexx-devel] CMake

Greetings P.O. P.O. Jonsson wrote: This will also require 2.8 rather than 2.6 for other platforms, which seems to make sense from the warnings received. Any objections? Ubuntu Xeniel, which is just rolling off of LTS support shortly has version: [ Source: cmake ] Package: cmake (3.5.1-1ubu

Re: [Oorexx-devel] CMake: not fetching correct svn revision, latest CMake gives a deprecation warning

On 28.10.2018 16:13, Erich Steinböck wrote: > > Jason, which version of ooRexx 5.0 do you use? > > > Rony, you may have posted this unintentionally here in this thread > Jason is running ooRexx on OpenIndiana, a SUN/Solaris fork Erich, you are right, it should have been a reply to his latest p

Re: [Oorexx-devel] CMake: not fetching correct svn revision, latest CMake gives a deprecation warning

> > Jason, which version of ooRexx 5.0 do you use? Rony, you may have posted this unintentionally here in this thread Jason is running ooRexx on OpenIndiana, a SUN/Solaris fork ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lis

Re: [Oorexx-devel] CMake: not fetching correct svn revision, latest CMake gives a deprecation warning

Jason, which version of ooRexx 5.0 do you use? Running the samples with rev 11503 work flawlessly on MacOSX and Linux in addition to Windows. ---rony On 28.10.2018 14:10, Rony G. Flatscher wrote: > Erich, > > On 27.10.2018 18:09, Erich Steinböck wrote: >> Rony, the issue with CMake not fetchi

Re: [Oorexx-devel] CMake: not fetching correct svn revision, latest CMake gives a deprecation warning

Erich, On 27.10.2018 18:09, Erich Steinböck wrote: > Rony, the issue with CMake not fetching the current SVN number should be > fixed with the latest > change to CMakeLists.txt in [r11506]. it works, great! ---rony ___ Oorexx-devel mailing list Oore

Re: [Oorexx-devel] CMake: not fetching correct svn revision, latest CMake gives a deprecation warning

Rony, the issue with CMake not fetching the current SVN number should be fixed with the latest change to CMakeLists.txt in [r11506]. ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] CMake: not fetching correct svn revision, latest CMake gives a deprecation warning

Just to add an observation on Linux (Ubuntu): when using cmake.org's CMake (version 3.12) then the svn revision number is 0, using Ubuntu's version of CMake (3.5.1) retrieves the version number, however it is not used in the names of the created rpm- and deb-packages. ---rony On 13.07.2018 15:

Re: [Oorexx-devel] CMake minimum version and policies.

Ad repository on mac: Homebrew: my preferred package handler for MacOS; almost anything can be fund there: https://brew.sh/index_de Another big package handler is MacPorts: https://www.macports.org/ Which one you use depends on your taste, both are just fine. Von meinen Macbook gesendet Häls

Re: [Oorexx-devel] CMake minimum version and policies.

For what it is worth I use cmake version 3.11.4 on a Mac running High Sierra and have seen no problems (but a lot of warnings for deprecated stuff). Von meinen Macbook gesendet Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 01.08.2018 um 21:35 schrieb Rick McGuire : > > Ok, I

Re: [Oorexx-devel] CMake minimum version and policies.

Ok, I rolled it back to 2.8. However, I also feel that lack of support on older platforms should not be something that should prevent us from using newer features in the future. Lack of support for new versions of development tooling should be a criteria that should be used to prune the supported s

Re: [Oorexx-devel] CMake minimum version and policies.

Also some of our Jenkins build server slaves can't build any more due to the minimum required CMake version change. Ubuntu 16.04 just has CMake 3.5 in it's repo, CentOS 7 just 2.8, and one of the macOS slaves is at 3.2 (is there such a thing as a repository on MacOS?). As long as there's no real f

Re: [Oorexx-devel] CMake minimum version and policies.

An update to the minimum version number. While trying to create ooRexx 5.0beta on Ubuntu I noticed that only version 3.5 was available there as of yesterday, which could not be used to build ooRexx as its minimum CMake level is set to 3.8. (Went to cmake.org and downloaded the latest version for

Re: [Oorexx-devel] CMake minimum version and policies.

Given the many projects for which I am using CMake, I would strongly recommend 3.5 or higher as the minimum base. VS 2017 includes integration support for 3.7.2 and higher. 3.8 introduces language level standards. Mark From: Rick McGuire Sent: Friday, July 13, 2018 6:28 AM To: Open Obje

Re: [Oorexx-devel] CMake: not fetching correct svn revision, latest CMake gives a deprecation warning

Tortoise svn works from the batch file after setting the environment, e.g. svn info --show-item revision F:\work\svn\oorexx\sandbox\rick\reference yields: 11460 ---rony On 13.07.2018 15:21, Rony G. Flatscher wrote: > On 13.07.2018 15:16, Rick McGuire wrote: >> I'm not seeing any issue

Re: [Oorexx-devel] CMake: not fetching correct svn revision, latest CMake gives a deprecation warning

On 13.07.2018 15:16, Rick McGuire wrote: > I'm not seeing any issue with retrieving the revision number. Do you have svn > in the path so that > CMake can find it? Yes, CMake reports "C:/Program Files/TortoiseSVN/bin/svn.exe", that is its location. > On Fri, Jul 13, 2018 at 6:19 AM Rony G. Fla

Re: [Oorexx-devel] CMake: not fetching correct svn revision, latest CMake gives a deprecation warning

I'm not seeing any issue with retrieving the revision number. Do you have svn in the path so that CMake can find it? Rick On Fri, Jul 13, 2018 at 6:19 AM Rony G. Flatscher wrote: > While creating the different ooRexx Windows installers I noticed that > CMake did not return the current svn revis

Re: [Oorexx-devel] Cmake problem

You are probably right about CMake not discovering missing requisites header files. I would open a bug on the CMake.org web site. In any case, it does crap out when it compiles. It is just that the message is not very informative. David Ashley On 03/02/2015 11:08 AM, CVBruce wrote: I did get

Re: [Oorexx-devel] Cmake problem

I did get ooRexx V5 (from the svn repository) to compile. The only problem I ran into was that although I had curses installed, I didn't have the curses-devl package, so my system didn't have the required curses.h. Shouldn't cmake discover this and report it during makefile creation? Bruce On

Re: [Oorexx-devel] Cmake problem

Upgrading CMake should fix the problem. The newer GCC should also fix the linker problem. David Ashley On 02/21/2015 09:39 AM, CVBruce wrote: Thanks Rick. So the cmake I'm using is the newest one in my Linux distro. I assume that I can manually install a newer version from CMake. Are there

Re: [Oorexx-devel] Cmake problem

Thanks Rick. So the cmake I'm using is the newest one in my Linux distro. I assume that I can manually install a newer version from CMake. Are there any other packages that would need to be upgraded? I'm aware of the gcc issues, and I have gcc 4.7 installed. Thanks again. Bruce On Feb 21,

Re: [Oorexx-devel] Cmake problem

I suspect this is a cmake version problem. I'm not sure what release the TIMESTAMP subcommand was implemented, but it is not in the 2.8.8 documdentation, but works on the 2.8.12.2 version I'm running. Rick On Sat, Feb 21, 2015 at 1:23 AM, CVBruce wrote: > Hi, > > I tried to compile ooRexx V5 o

Re: [Oorexx-devel] [CMake] Problems resolving PTHREAD_* symbols.

I've fixed the other problems and David committed a fix that might fix the Mac build also that is other than the change to REQUIRED_LIBRARIES. I've been able to test that fix on one of the platforms we need to build on and it seemed ok, but I think David will need to check this out using the build

Re: [Oorexx-devel] [CMake] Problems resolving PTHREAD_* symbols.

Hello all, for an oversight in my apple-mail configuration my first post on the topic got lost in the network ( I do not find it in the archives ) here is the original post I guess I found the error/oversight the original CMakelists contains a set(CMAKE_REQUIRED_LIBRARIES “pthread;pthread

Re: [Oorexx-devel] [CMake] Problems resolving PTHREAD_* symbols.

another follow on :-) there a typo in config.h.in.cmake line 196 should be #define PACKAGE_NAME ${PACKAGE_NAME} enrico -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Sta

Re: [Oorexx-devel] [CMake] Problems resolving PTHREAD_* symbols.

Follow on, now the build is successful on apple I found the oversight in rxsockfn.cpp at statement 89 instead of #if defined(OPSYS_AIX) || defined(OPSYS_LINUX) it is necessary to use #if defined(OPSYS_AIX) || defined(OPSYS_LINUX) || defined(OPSYS_DARWIN) and … [enrico@enrico-mbp bin]$./rexx -v

Re: [Oorexx-devel] CMake build; MutableBuffer missing caselessPos

Oops, made a copy error...or more precisely, a "forget to copy error" :-) Rick On Mon, Jun 16, 2014 at 5:07 PM, Mark Miesfeld wrote: > With a CMake build, the MutableBuffer class is missing caselessPos: > > C:\work.ooRexx\wc\ooTest\4.x>qtest.rex > 3 *-* say .mutablebuffer~new('Saturday')~

Re: [Oorexx-devel] CMake build and NSIS installer.

A couple of additional points on the installer, but these issues can be solved once we have the main installer working. Right now, I only have two components defined in CMakeLists.txt, Core and DevLib. The Samples component is easy, really just a matter of adding a bunch of install commands, but

Re: [Oorexx-devel] cmake and man pages

Went back to the original commit for this macro and it looked correct to me, assuming the old logic was correct. A later commit by David turned the location into a relative location. Rick On Sun, May 25, 2014 at 12:35 AM, Moritz Hoffmann wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA2

Re: [Oorexx-devel] cmake and man pages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I guess this is my mistake ;-) I basically converted the several install commands for each man page to a macro to avoid code duplication in the cmake file. Moritz On 05/24/2014 09:15 PM, Rick McGuire wrote: > Ok, on further investigation, share/man

Re: [Oorexx-devel] cmake and man pages

Ok, on further investigation, share/man/man1/.1.gz does look like it is the correct location, although I do wonder about the relative path specified in the install command. Rick On Sat, May 24, 2014 at 2:47 PM, Rick McGuire wrote: > I'm not sure if this is correct or not, but this link gives i

Re: [Oorexx-devel] CMake Status - RPM and DEB Install files

David, I was looking through the CMake documentation this morning and discovered the configure_file() command. That might make fixing the hard coded stuff a piece of cake by using a template file for the scripts. Rick On Fri, May 23, 2014 at 11:19 AM, David Ashley wrote: > All - > > I have mos

Re: [Oorexx-devel] CMake Status - RPM and DEB Install files

Greeting David, David Ashley wrote: > 1. The Ubuntu installer still complains about a control file that does > not have the correct permission in the package. I have no idea what the > control file is as the message does not name it. Perhaps this document might be of assistance: https://www.deb

Re: [Oorexx-devel] CMake Man Page Macro Not Working

David, if I'm reading the messages correctly, it looks like the conflict is with "man1", not with something in man1. I suggest looking at the generated .qz file to see if contains what it should. It might be trying to overwrite the man1 directory rather than installing files in the man1 directory

Re: [Oorexx-devel] CMake Man Page Macro Not Working

David, I think Moritz added that, not me. Rick On Thu, May 22, 2014 at 11:59 AM, David Ashley wrote: > Rick - > > For some reason, your new man page macro is not working or something > else has been added to the mix. I get the following useless error > message when I try to install the rpm. >

Re: [Oorexx-devel] CMake Man Page Macro Not Working

I have no idea what you're talking about. I've not done anything with man pages...I'm going to need a little more context. Rick On Thu, May 22, 2014 at 11:59 AM, David Ashley wrote: > Rick - > > For some reason, your new man page macro is not working or something > else has been added to the m

Re: [Oorexx-devel] CMake deb

Hi David, Well, it looks like being slow works our pretty well. It seems this is fixed. ;-) -- Mark Miesfeld On Mon, May 19, 2014 at 1:55 PM, David Ashley wrote: > Mark - > > If you get some time please look at the CMake for a deb output install > file. Currently, it does not work. > > 1. T

Re: [Oorexx-devel] CMake deb

David, This might be one of those D'oh type errors. I think the variable for specifying the control scripts is CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA, not CPACK_DEBIAN_CONTROL_EXTRA. See http://www.cmake.org/Wiki/CMake:CPackPackageGenerators#control_file_.28aka_DEBIAN.2Fcontrol.29_for_binary_packag

Re: [Oorexx-devel] CMake deb

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi there, comments inline. M On 05/19/2014 10:55 PM, David Ashley wrote: > Mark - > > If you get some time please look at the CMake for a deb output > install file. Currently, it does not work. > > 1. The files all get installed. 2. The post insta

Re: [Oorexx-devel] CMAKE out-of-source builds

One additional (but very important point) I need to make about this. I just spent a couple of hours pulling my hair out trying to figure out why cmake was writing all of the files to the root of the source tree rather than to the current directory. It turns out the source of the problem was I had

Re: [Oorexx-devel] CMAKE out-of-source builds

Probably a good idea. I'm probably checking some changes in fairly shortly, so I'll take care of deleting it. Rick On Tue, May 13, 2014 at 3:13 PM, David Ashley wrote: > We should remove the build subdir if we are going to use this method to > avoid confusion. > > David Ashley > > On Tue, 2014

Re: [Oorexx-devel] CMAKE out-of-source builds

We should remove the build subdir if we are going to use this method to avoid confusion. David Ashley On Tue, 2014-05-13 at 13:26 -0400, Rick McGuire wrote: > I've been doing a bit of reading up on CMake, and there's one aspect > of it I think needs to be pointed out since it requires a small cha

Re: [Oorexx-devel] CMAKE and the files generated from XSL.

I like the idea of generating the files in a separate process. That way it keeps the CMake build clean and straightforward. Oh, and the Linux version of the script to generate the files using Xalan is really simple so no problem there. David Ashley On Fri, 2014-05-02 at 06:31 -0400, Rick McGuire

Re: [Oorexx-devel] cmake problems on Windows with latest update.

Ok, found the --debug-output option which spotlighted the error. The RexxMain.cpp source file only exists in the unix platform directory. It's an AIX compatibility stub that doesn't apply to Windows. That will need to be made conditional. Rick On Fri, May 2, 2014 at 7:08 AM, Rick McGuire wrot

Re: [Oorexx-devel] cmake problems on Windows with latest update.

Hmmm, the error and output logs are essentially identical between the two cases as well. Not real useful diagnostics. Rick On Fri, May 2, 2014 at 7:03 AM, Rick McGuire wrote: > David, > > I thought I would try out your latest update to try to help out with the > compile errors your checkin co

Re: [Oorexx-devel] CMake Starter File Commited

I'm willing to live with that, if we can get it to work cross platform. I'm having some serious issues with it on Windows with building in 64-bit mode. I've done some searches, and it appears to be a common problem, but I've not seen any real solutions offered other than to use the Visual Studio

Re: [Oorexx-devel] CMake Starter File Commited

Agreed. The output of CMake was not as I expected (one or more makefiles). I guess we need to decide if having CMAKE as a hard requirement to build ooRexx is acceptable or not. David Ashley On Thu, 2014-05-01 at 06:41 -0400, Rick McGuire wrote: > One additional observation about cmake. The gener

Re: [Oorexx-devel] CMake Starter File Commited

Ok, I took a peek at the cmake master file and spotted the error. The lines that set up the include path were inside a conditional block. I moved them outside the conditional, and the compiles worked. Now I'm seeing link errors that appear to suggest things are getting confused between 32- and 6

Re: [Oorexx-devel] CMake Starter File Commited

Ok, poking around in the generated build files, I found the definition of CXX_FLAGS in rexxapi.dir\flags.make. Here it is: CXX_FLAGS = /DWIN32 /D_WINDOWS /W3 /GR /EHsc /D_DEBUG /MDd /Zi /Ob0 /Od /RTC1 -IC:\ORexxDev\oorexx\api\platform\windows -IC:\ORexxDev\oorexx\api The only include directori

Re: [Oorexx-devel] CMake Starter File Commited

One additional observation about cmake. The generated makefile leans very heavily on the cmake utilities to do the build, so it does not look like it would be feasible to use cmake to generate the files and then just check them into the build for anybody who does not want to install cmake. cmake

Re: [Oorexx-devel] CMake Starter File Commited

OK, figured out how to get it go generate nmake files. The secret is to add -G "NMake Makefiles" to the cmake command. Again, this generated without error, but when I run nmake, it again gives compile errors that appear to indicate the include path is not getting setup correctly. Here is the build

Re: [Oorexx-devel] CMake Starter File Commited

Just did this, and it looks like there is a problem if you have the full visual studio installed. It is generating a Visual Studio project rather than a makefile. I opened that project in VS, and it did not build cleanly because it was not finding any of the project header files that needed to be

Re: [Oorexx-devel] CMake Starter File Commited

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, this is great! Thanks for the effort. Just tried it and it successfully builds the shared library. cmake complains about some syntax errors in CMakeLists.txt:171 but I guess you can see them yourself as well. Moritz On 05/01/2014 02:42 AM, Davi