|
CMake and CINT tests
|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
 |
CMake and CINT tests
by Zelzer Sascha
::
Rate this Message:
Hi,
CINT now compiles under Windows using the CMake Visual Studio 9 project generator. I am now looking at integrating the CINT tests into the CMake testing infrastructure. Unfortunately there are some problems related to the use of makecint in testall.cxx. - Because testall.cxx relies on the makecint tool and directly calls "make", a cygwin environment with GNU make would be necessary to run the tests right now (so there would be no benefit of having a CMake based build system). I see the following possible solutions: 1.) The cleanest way would probably be to rewrite the whole testall.cxx script in terms of CMake macros and commands. This would be quite some work and result in additional maintenance (in addition to maintain the normal CMake build scripts along the make files for probably some time). 2.) Rewrite the testall.cxx script (and possibly makecint) such that it is sensitive to the build environment, i.e. that it calls "make" in a POSIX environment, "nmake" under Windows NMake environment (supposing makecint generates nmake conforming makefiles) or "cmake -P somescript.cmake" if CMake is available in order to call CMake macros for generating dictionaries and small Visual Studio or nmake project files to compile them. I would appreciate your feedback about how you feel to proceed. Alternatively, I could finish (polish) the current CMake files without testing support. Regards, Sascha |
|
|
Re: CMake and CINT tests
by Philippe Canal
::
Rate this Message:
Hi,
My preference goes toward upgrading makecint to be able to generate CMake scripts using the new general rules. Cheers, Philippe. Zelzer Sascha wrote: > Hi, > > CINT now compiles under Windows using the CMake Visual Studio 9 project > generator. I am now looking at integrating the CINT tests into the CMake > testing infrastructure. Unfortunately there are some problems related to > the use of makecint in testall.cxx. > > - Because testall.cxx relies on the makecint tool and directly calls > "make", a cygwin environment with GNU make would be necessary to run the > tests right now (so there would be no benefit of having a CMake based > build system). > > I see the following possible solutions: > > 1.) The cleanest way would probably be to rewrite the whole testall.cxx > script in terms of CMake macros and commands. This would be quite some > work and result in additional maintenance (in addition to maintain the > normal CMake build scripts along the make files for probably some time). > > 2.) Rewrite the testall.cxx script (and possibly makecint) such that it > is sensitive to the build environment, i.e. that it calls "make" in a > POSIX environment, "nmake" under Windows NMake environment (supposing > makecint generates nmake conforming makefiles) or "cmake -P > somescript.cmake" if CMake is available in order to call CMake macros > for generating dictionaries and small Visual Studio or nmake project > files to compile them. > > I would appreciate your feedback about how you feel to proceed. > Alternatively, I could finish (polish) the current CMake files without > testing support. > > Regards, > Sascha > > |
|
|
Re: CMake and CINT tests
by Axel Naumann
::
Rate this Message:
Hi,
agreed, but it should not cause any delay. I.e. if for now we cannot run the tests with CMake (worst option), or we can only run them if GNU make is available (_much_ better option) than that would be fine with me, too. In the end havign makecint spit out CMake files would definitely be optimal. Cheers, Axel. On 2009-02-03 17:54, Philippe Canal wrote: > Hi, > > My preference goes toward upgrading makecint to be able to generate > CMake scripts using > the new general rules. > > Cheers, > Philippe. > > Zelzer Sascha wrote: >> Hi, >> >> CINT now compiles under Windows using the CMake Visual Studio 9 project >> generator. I am now looking at integrating the CINT tests into the CMake >> testing infrastructure. Unfortunately there are some problems related to >> the use of makecint in testall.cxx. >> >> - Because testall.cxx relies on the makecint tool and directly calls >> "make", a cygwin environment with GNU make would be necessary to run the >> tests right now (so there would be no benefit of having a CMake based >> build system). >> >> I see the following possible solutions: >> >> 1.) The cleanest way would probably be to rewrite the whole testall.cxx >> script in terms of CMake macros and commands. This would be quite some >> work and result in additional maintenance (in addition to maintain the >> normal CMake build scripts along the make files for probably some time). >> >> 2.) Rewrite the testall.cxx script (and possibly makecint) such that it >> is sensitive to the build environment, i.e. that it calls "make" in a >> POSIX environment, "nmake" under Windows NMake environment (supposing >> makecint generates nmake conforming makefiles) or "cmake -P >> somescript.cmake" if CMake is available in order to call CMake macros >> for generating dictionaries and small Visual Studio or nmake project >> files to compile them. >> >> I would appreciate your feedback about how you feel to proceed. >> Alternatively, I could finish (polish) the current CMake files without >> testing support. >> >> Regards, >> Sascha >> >> > > |
|
|
AW: CMake and CINT tests
by Zelzer Sascha
::
Rate this Message:
Hi,
okay, let's do it this way. Unfortunately, I am very busy with my own project right now (we have to meet a deadline end of march), so I would suggest that I finish the CMake files without extensive testing support and send them to you. Hopefully this will be sometime next week. After march, I hope to be able to look again into integrating the tests (if you solved it already at this time, that's fine with me ;-) ) Regards, Sascha > -----Ursprüngliche Nachricht----- > Von: Axel Naumann [mailto:Axel.Naumann@...] > Gesendet: Mittwoch, 4. Februar 2009 15:20 > An: Zelzer Sascha > Cc: Philippe Canal; cint@... > Betreff: Re: [CINT] CMake and CINT tests > > Hi, > > agreed, but it should not cause any delay. I.e. if for now we cannot > run > the tests with CMake (worst option), or we can only run them if GNU > make > is available (_much_ better option) than that would be fine with me, > too. In the end havign makecint spit out CMake files would definitely > be > optimal. > > Cheers, Axel. > > On 2009-02-03 17:54, Philippe Canal wrote: > > Hi, > > > > My preference goes toward upgrading makecint to be able to generate > > CMake scripts using > > the new general rules. > > > > Cheers, > > Philippe. > > > > Zelzer Sascha wrote: > >> Hi, > >> > >> CINT now compiles under Windows using the CMake Visual Studio 9 > project > >> generator. I am now looking at integrating the CINT tests into the > CMake > >> testing infrastructure. Unfortunately there are some problems > related to > >> the use of makecint in testall.cxx. > >> > >> - Because testall.cxx relies on the makecint tool and directly calls > >> "make", a cygwin environment with GNU make would be necessary to run > the > >> tests right now (so there would be no benefit of having a CMake > based > >> build system). > >> > >> I see the following possible solutions: > >> > >> 1.) The cleanest way would probably be to rewrite the whole > testall.cxx > >> script in terms of CMake macros and commands. This would be quite > some > >> work and result in additional maintenance (in addition to maintain > the > >> normal CMake build scripts along the make files for probably some > time). > >> > >> 2.) Rewrite the testall.cxx script (and possibly makecint) such that > it > >> is sensitive to the build environment, i.e. that it calls "make" in > a > >> POSIX environment, "nmake" under Windows NMake environment > (supposing > >> makecint generates nmake conforming makefiles) or "cmake -P > >> somescript.cmake" if CMake is available in order to call CMake > macros > >> for generating dictionaries and small Visual Studio or nmake project > >> files to compile them. > >> > >> I would appreciate your feedback about how you feel to proceed. > >> Alternatively, I could finish (polish) the current CMake files > without > >> testing support. > >> > >> Regards, > >> Sascha > >> > >> > > > > |
|
|
Re: AW: CMake and CINT tests
by Axel Naumann
::
Rate this Message:
Hi Sascha,
sounds good! Cheers, Axel. Zelzer Sascha wrote: > Hi, > > okay, let's do it this way. Unfortunately, I am very busy with my own project right now (we have to meet a deadline end of march), so I would suggest that I finish the CMake files without extensive testing support and send them to you. Hopefully this will be sometime next week. After march, I hope to be able to look again into integrating the tests (if you solved it already at this time, that's fine with me ;-) ) > > Regards, > Sascha > >> -----Ursprüngliche Nachricht----- >> Von: Axel Naumann [mailto:Axel.Naumann@...] >> Gesendet: Mittwoch, 4. Februar 2009 15:20 >> An: Zelzer Sascha >> Cc: Philippe Canal; cint@... >> Betreff: Re: [CINT] CMake and CINT tests >> >> Hi, >> >> agreed, but it should not cause any delay. I.e. if for now we cannot >> run >> the tests with CMake (worst option), or we can only run them if GNU >> make >> is available (_much_ better option) than that would be fine with me, >> too. In the end havign makecint spit out CMake files would definitely >> be >> optimal. >> >> Cheers, Axel. >> >> On 2009-02-03 17:54, Philippe Canal wrote: >>> Hi, >>> >>> My preference goes toward upgrading makecint to be able to generate >>> CMake scripts using >>> the new general rules. >>> >>> Cheers, >>> Philippe. >>> >>> Zelzer Sascha wrote: >>>> Hi, >>>> >>>> CINT now compiles under Windows using the CMake Visual Studio 9 >> project >>>> generator. I am now looking at integrating the CINT tests into the >> CMake >>>> testing infrastructure. Unfortunately there are some problems >> related to >>>> the use of makecint in testall.cxx. >>>> >>>> - Because testall.cxx relies on the makecint tool and directly calls >>>> "make", a cygwin environment with GNU make would be necessary to run >> the >>>> tests right now (so there would be no benefit of having a CMake >> based >>>> build system). >>>> >>>> I see the following possible solutions: >>>> >>>> 1.) The cleanest way would probably be to rewrite the whole >> testall.cxx >>>> script in terms of CMake macros and commands. This would be quite >> some >>>> work and result in additional maintenance (in addition to maintain >> the >>>> normal CMake build scripts along the make files for probably some >> time). >>>> 2.) Rewrite the testall.cxx script (and possibly makecint) such that >> it >>>> is sensitive to the build environment, i.e. that it calls "make" in >> a >>>> POSIX environment, "nmake" under Windows NMake environment >> (supposing >>>> makecint generates nmake conforming makefiles) or "cmake -P >>>> somescript.cmake" if CMake is available in order to call CMake >> macros >>>> for generating dictionaries and small Visual Studio or nmake project >>>> files to compile them. >>>> >>>> I would appreciate your feedback about how you feel to proceed. >>>> Alternatively, I could finish (polish) the current CMake files >> without >>>> testing support. >>>> >>>> Regards, >>>> Sascha >>>> >>>> >>> > > |
| Free embeddable forum powered by Nabble | Forum Help |
