2012/7/10 jupiter :
> Hi,
>
> I need to run shell script to do following check and to install
> configure files during RPM installation:
>
> if config files installed in /etc/myconfig, rename files in
> /etc/myconfig and copy new config files to /etc/myconfig;
> else copy config files to /etc/mycon
Ateljevich, Eli wrote:
> Hi all,
> I am doing an out-of-source build in a directory called /build. I have a
> test directory /examples that has some input to be run with the projects
> main driver:
>
> /proj
>/build
> /bin
> driver.exe
> /example1
> /example2
>/e
Hi all,
I am doing an out-of-source build in a directory called /build. I have a test
directory /examples that has some input to be run with the projects main driver:
/proj
/build
/bin
driver.exe
/example1
/example2
/example
/example1
...some files
I'm not exactly sure what you are asking, but I think that rpm takes
care of moving old files by renaming them to .rpmorig. As an alternative
it is possible to pass your own rpm spec file to cmakerpm and there you
can use pre- and postinstallation hooks to do what you want.
Micha
On 07/10/201
Hi,
I need to run shell script to do following check and to install
configure files during RPM installation:
if config files installed in /etc/myconfig, rename files in
/etc/myconfig and copy new config files to /etc/myconfig;
else copy config files to /etc/myconfig
Is there a simple way to do i
My source and tests are stored separately in a quasi-parallel arrangement:
/proj
/build
/bin # CMAKE_RUNTIME_OUTPUT_DIRECTORY
/mod1 # Build directory
/mod2
/test
/mod1
/mod2
/src # source
/mod1
/mod2
/test # sourc
On Wed, Jul 4, 2012 at 6:41 AM, hce wrote:
>
> Rolf Eike Beer wrote
> >
> > Of course it does, because the drop site is not set. And CTest should
> > really
> > be tought to do something sensible then and not trying to contact the
> > universe
> > and then complain it doesn't listen.
> >
>
> So b
you should always use cmake to build out-of-source. or something like
a 'build' directory in the source...
On Mon, Jul 9, 2012 at 9:32 AM, Romain LEGUAY wrote:
> Thanks for your answer!
>
> But I think if I do a 'cmake .' in lib dir or a application folder, I am
> going to have some problem no?
Thanks for your answer!
But I think if I do a 'cmake .' in lib dir or a application folder, I am
going to have some problem no?
Romain
Le 09/07/12 18:14, J Decker a écrit :
${CMAKE_SOURCE_DIR} this is the directory of the root CMakeLists.txt
that is processing, you can base your other paths
${CMAKE_SOURCE_DIR} this is the directory of the root CMakeLists.txt
that is processing, you can base your other paths off of that.
On Mon, Jul 9, 2012 at 6:58 AM, Romain LEGUAY wrote:
> Hello everyone,
>
> I have a big project organized like this:
> root/
> -> CMakeLists.txt
> CM
On 9 July 2012 14:20, Rolf Eike Beer wrote:
> The reason is very likely that MS compilers are broken regarding the
> difference between <> and "" in #include statements,
Please, refer to
- C99 standard (e.g. N1336), 6.10.2 Source file inclusion, clause 1 and 2
- C++ standard (e.g. N3290), 16.2 So
Hello everyone,
I have a big project organized like this:
root/
-> CMakeLists.txt
CMake/
--> some .cmake scripts
lib/
--> CMakeLists.txt
include/
src/
CMake/
--> some .cmake scripts
apps/
Hi all.
Actually, the MS compilers distinguish <> and "" just fine (at least
in my VS 2005 and VS 2010 installation). Dominik, do you perhaps
specify the path to your Math.h in include_directories()?
Petr
On Mon, Jul 9, 2012 at 3:20 PM, Rolf Eike Beer wrote:
> Am 09.07.2012 15:07, schrieb Domin
Am 09.07.2012 15:07, schrieb Dominik Szczerba:
Thanks a lot for your hints. I managed to find the problem. By some
unclear reason iostream or one of its sub-includes includes math.h
and
very strangely does not take the one in the system folder, instead
taking my local file called Math.h in the
On 07/09/2012 08:41 AM, Brad King wrote:
Of course, at the end of the day this is what breaks GNAT TryCompile:
- targetName = "cmTryCompileExec";
But not removing that line of code would seemingly break everything else.
So the path of least resistance cynical code change proposal:
#ifdef __li
Thanks a lot for your hints. I managed to find the problem. By some
unclear reason iostream or one of its sub-includes includes math.h and
very strangely does not take the one in the system folder, instead
taking my local file called Math.h in the same folder as test.cxx
(Windows names are unfortun
On 07/06/2012 07:46 AM, Matthew Schuchard wrote:
> I thought the change had been to preserve prior TryCompiles for
> debugging purposes.
> Would it be too cynical to propose some OS #ifdefs above the code?
> Although you mention file systems, so this an NTFS issue also?
We don't know what causes
On 9 July 2012 12:12, Dominik Szczerba wrote:
> Hi,
>
> In one, but not another, cmake-based bigger C++ project I am getting
> the following errors trigger by a test.cxx file consiting only of one
> line: #include .
>
> 1>c:\Program Files (x86)\Microsoft Visual Studio
> 10.0\VC\include\string(543)
Hi,
In one, but not another, cmake-based bigger C++ project I am getting
the following errors trigger by a test.cxx file consiting only of one
line: #include .
1>c:\Program Files (x86)\Microsoft Visual Studio
10.0\VC\include\string(543): error C2039: '_Stolx' : is not a member
of '`global namespa
On 9 July 2012 11:47, Georgios Petasis wrote:
> I want to build 32-bit binaries on a 64-bit Linux system, with gcc.
> In projects that use configure, this is easy:
>
> export CFLAGS=-m32
>
> But how can I do the same with cmake projects?
You do the same
> cmake does not seem to use CFLAGS. Is th
Hi all,
I want to build 32-bit binaries on a 64-bit Linux system, with gcc.
In projects that use configure, this is easy:
export CFLAGS=-m32
But how can I do the same with cmake projects?
cmake does not seem to use CFLAGS. Is there a variable I can define when
I run cmake, to pass the -m32 fl
Done: http://public.kitware.com/Bug/view.php?id=13385
--Zaheer
On Mon, Jul 9, 2012 at 8:15 AM, Brett Delle Grazie
wrote:
>
> On Jul 8, 2012 10:59 PM, "Zaheer Chothia" wrote:
>>
>> Hello,
>>
>> I posted a mail here [1] but have yet to receive any replies. I think my
>> last
>> message was too l
On 8 July 2012 13:34, Mateusz Loskot wrote:
> Hi,
>
> I'm porting build configuration based on GNU Autotools to CMake
> and I have to deal with C preprocessing to generate a file.
>
> The input for preprocessor is SQL file with C preprocessor directives
> used, like #include "another.sql", etc.
>
Hi Mateusz,
I am not aware of direct cmake support for preprocessing a file, so I
will only comment on the add_custom_*() part.
You have to create a custom command (using the OUTPUT signature) to
actually do the preprocessing. If you're targetting gcc and Visual
Studio, the command could look som
24 matches
Mail list logo
