Re: [CMake] Cmake/Cpack creates a corrupt .rpm

2019-05-30 Thread Zan Lynx
On May 30, 2019 5:21:59 PM MST, "Gonzalo Garramuño" wrote: > >El 30/5/19 a las 12:51, Gonzalo Garramuño escribió: >> rpm -ql mrViewer-v5.0.6-Linux-64.rpm > >If I run cpio -i < mrViewer-v5.0.6-Linux-64.rpm > >I get a bunch of warnings of Incorrect numbers (and garbage) and Cannot > >make mknod:

Re: [CMake] RC compilation failing

2019-04-09 Thread Zan Lynx
On April 9, 2019 1:51:52 PM MDT, "Gonzalo Garramuño" wrote: >I had a resource.rc file and a resource.h file with just an ICON to >provide the icon to my application.  However, since a week or so ago, >RC >refuses to compile it, giving the not very helpful message: > >Microsoft (R) Windows (R)

Re: [CMake] further configuration of generated projects outside of CMake?

2019-03-11 Thread Zan Lynx
On March 11, 2019 6:03:24 PM MDT, hex wrote: >hi everyone, > >There are many generators supported in CMake. A CMake build system >allows me to generate the preferred build environment for everyone, >visual studio, eclipse, ninja you name it. > >The problem I see with this is that projects are

Re: [CMake] Default CMAKE_C_FLAGS value by OS

2017-02-16 Thread Zan Lynx
On 02/16/2017 08:07 AM, Chuck Atkins wrote: > That being said, I do think we should revisit the use of O3 by default > given the safety issues surounding it. The following is just my opinion: In my experience if O3 fails it is a bug in the compiler, which should be fixed and somebody has to find

Re: [CMake] Comaptibility with older gcc

2017-01-27 Thread Zan Lynx
On 1/27/2017 10:04 AM, Michele Portolan wrote: I have a project that build correctly using gcc 4.9.3, generating a dynamic library that I can later link to obtain my executables. So, nothing special. My problem is that on one of my target systems, I only have a gcc 4.1.2 and I am forced to use

Re: [CMake] Single Letter Omissions From File Path In Linker

2016-10-14 Thread Zan Lynx
On 10/14/2016 08:04 AM, Randy Turner wrote: > As you can see, the file path is missing a "t" in the first occurrence > of the word "iterator" and so that file definitely does not exist. A > file exists in the location with correct spelling, but somehow that > hardcoded path in that temporary file