Am 14.01.2019 um 18:51 schrieb Erich Steinböck :
>> cleaning the build directory with "rm -rf *"
> Rony, I never remove the build directory. If I want to run a clean CMake, I
> use `rm CMakeCache.txt`
Very interesting, thank you very much, Erich!
—-rony
_
>
> cleaning the build directory with "rm -rf *"
Rony, I never remove the build directory. If I want to run a clean CMake, I
use `rm CMakeCache.txt`
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/list
>
> Since you have access to the different build machines, can you make this
> change? Does this remove the need for the Clang change?
I just committed CMake changes for C++11. I've also removed the two
CLANG-specific set lines as a test compile on macOS 10.14 runs fine without
them.
Just tested that: MacOS builds Linux gcc gets an error during compilation.
---rony
P.S.: While cleaning the build directory with "rm -rf *" I mistakingly deleted
my home directory
"~" so I will not be able to create builds for ooRexx or BSF4ooRexx for Linux
32- and 64-bit. :-(
[As I alotted t
Yes, the version I tested on before making the commit.
Rick
On Sun, Jan 13, 2019 at 12:40 PM Rony G. Flatscher
wrote:
> On 13.01.2019 18:27, Erich Steinböck wrote:
> > Those two SET's were the fix for
> https://sourceforge.net/p/oorexx/bugs/1577
> > Specific to CLANG on mac. That's probably th
Since you have access to the different build machines, can you make this
change? Does this remove the need for the Clang change?
Rick
On Sun, Jan 13, 2019 at 12:28 PM Erich Steinböck
wrote:
> Those two SET's were the fix for
> https://sourceforge.net/p/oorexx/bugs/1577
> Specific to CLANG on ma
On 13.01.2019 18:27, Erich Steinböck wrote:
> Those two SET's were the fix for https://sourceforge.net/p/oorexx/bugs/1577
> Specific to CLANG on mac. That's probably the reason why the mac builds
> don't give those c++11
> warnings.
Interestingly there are no such warnings issued when compiling
Those two SET's were the fix for https://sourceforge.net/p/oorexx/bugs/1577
Specific to CLANG on mac. That's probably the reason why the mac builds
don't give those c++11 warnings.
There's a new CMake 3.1 set (CMAKE_CXX_STANDARD 11)
And
https://stackoverflow.com/questions/10851247/how-to-activate
Hmm, the following lines in CMakeLists.txt look suspicious. I think the SET
commands should be outside the conditional.
# Extra link library definitions# gcc (at least on Linux) requires
linking with -lcrypt# clang (at least on Darwin) doesn't have
libcryptif (CMAKE_CXX_COMPILER_ID STREQUAL "GNU")
It probably just needs a compiler option added since the compiler is
obviously recognizing the feature. I really did find a lot of errors by
enabling this, so was a good thing to use. There are other c++1 classes
that are getting used, and this standard IS seven years old now, it's time
to move for
I only now notice that on our Ubuntu, CentOS and SLES/390 build slaves
we're seeing 5 build warnings of the kind
/home/netrexx/workspace/ooRexx-CentOS7-build/rexxapi/client/LocalRegistrationManager.hpp:69:63:
warning: override controls (override/final) only available with -std=c++11
or -std=gn
11 matches
Mail list logo
