On Friday 05 June 2009, Robert Haines wrote:
> Hi,
>
> On 5 Jun 2009, at 15:52, Prasad H. L. wrote:
> > I tried as you have suggested. I have one more problem. I tried the
> > following CMakeLists.txt
> >
> >
> > project(cmake_test)
> > cmake_minimum_required(VERSION 2.6)
> >
> > add_execu
On 5. Jun, 2009, at 22:27, Prasad H. L. wrote:
Consolidating all the things, the working CMakeLists.txt is as
follows -
project(cmake_test)
cmake_minimum_required(VERSION 2.6)
macro(m4tocxx outfilename)
add_custom_command(
OUTPUT ${CMAKE_CURRENT_
Consolidating all the things, the working CMakeLists.txt is as follows -
project(cmake_test)
cmake_minimum_required(VERSION 2.6)
macro(m4tocxx outfilename)
add_custom_command(
OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/${outfilename}.cpp
COMMAND m4 -P
Can I define a new source type, like .m4 and add rules for it? That
would be ideal, I feel, for my case.
2009/6/5 Tyler Roscoe :
> On Fri, Jun 05, 2009 at 10:10:07PM +0530, Prasad H. L. wrote:
>> 2009/6/5 Denis Scherbakov :
>> >
>> >> Is it possible to set the preprocessing to all .m4 files
>> >>
On Fri, Jun 05, 2009 at 10:10:07PM +0530, Prasad H. L. wrote:
> 2009/6/5 Denis Scherbakov :
> >
> >> Is it possible to set the preprocessing to all .m4 files
> >> avoiding a
> >> manual specification of list of files to processed?
> >
> > If your list of files changes all the time, you can use FILE
2009/6/5 Denis Scherbakov :
>
>> Is it possible to set the preprocessing to all .m4 files
>> avoiding a
>> manual specification of list of files to processed?
>
> I don't know of such, but it does not mean that it does not exist.
>
> If your list of files changes all the time, you can use FILE(GLOB
> Is it possible to set the preprocessing to all .m4 files
> avoiding a
> manual specification of list of files to processed?
I don't know of such, but it does not mean that it does not exist.
If your list of files changes all the time, you can use FILE(GLOB...)
to find all *.m4 files to automat
Thanks.
Is it possible to set the preprocessing to all .m4 files avoiding a
manual specification of list of files to processed?
2009/6/5 Denis Scherbakov :
>
>
>> 'm4' outputs only on stdout and does not have an option to
>> specify the
>> output file. Please
>> suggest me a solution for this...
Hi,
On 5 Jun 2009, at 15:52, Prasad H. L. wrote:
I tried as you have suggested. I have one more problem. I tried the
following CMakeLists.txt
project(cmake_test)
cmake_minimum_required(VERSION 2.6)
add_executable(testcmake testcmake.m4.cpp)
add_custom_command(OUTPUT testcmake.m4.cpp
> 'm4' outputs only on stdout and does not have an option to
> specify the
> output file. Please
> suggest me a solution for this...
I had a similar problem and also with a preprocessor. I ended up writing
a CMake script like this:
EXECUTE_PROCESS(
COMMAND my-command "${VAR_IFILE}"
RESULT_V
I tried as you have suggested. I have one more problem. I tried the
following CMakeLists.txt
project(cmake_test)
cmake_minimum_required(VERSION 2.6)
add_executable(testcmake testcmake.m4.cpp)
add_custom_command(OUTPUT testcmake.m4.cpp
m4 -P -s tes
> I wanted to do some looping in macros which are not
> possible in GNU
> CPP. So, I wrote
> macros in m4. I wish to pre-process all my C/C++ code with
> m4 before
> handing it over to
> gcc. I did not find any direct way out for doing this in
> cmake. Any
> ideas how to do it with
> cmake?
Use
Hi,
I wanted to do some looping in macros which are not possible in GNU
CPP. So, I wrote
macros in m4. I wish to pre-process all my C/C++ code with m4 before
handing it over to
gcc. I did not find any direct way out for doing this in cmake. Any
ideas how to do it with
cmake?
Regards,
Prasad
_
13 matches
Mail list logo
