On Saturday, June 04, 2011 01:28:51 AM Dan Furtney wrote:
> I need to perform cross compile builds for three different types of VxWorks
> compilers. I was able to build a simple program using the strategy
> provided on the wiki. This, however, does not let me target the a specific
> linker and scri
so what is the proper way for someone without repository write access
to get patches added?
On Tue, Feb 15, 2011 at 3:27 PM, J Decker wrote:
> http://public.kitware.com/Bug/view.php?id=11866
>
___
Powered by www.kitware.com
Visit other Kitware open-sou
I need to perform cross compile builds for three different types of VxWorks
compilers. I was able to build a simple program using the strategy provided on
the wiki. This, however, does not let me target the a specific linker and
scripts I need at link time.
Is development of a VxWorks.cmake pr
My Computer -> View System Information -> Advanced -> Environment
Variables -> System Variables -> Path -. Edit (or New) ->
C;/MinGW/bin;...
On Fri, Jun 3, 2011 at 4:47 PM, David Cole wrote:
> On Fri, Jun 3, 2011 at 4:36 PM, Bill Lorensen wrote:
>> Dave,
>>
>> Exactly what I see unless I add c
On Fri, Jun 3, 2011 at 4:36 PM, Bill Lorensen wrote:
> Dave,
>
> Exactly what I see unless I add c:/MinGW/bin to the windows system
> Path (not PATH). cmake-gui fails, but the msys shell works fine.
>
> Bill
>
How do you add it to the Path (not PATH)??
(Give me step-by-step, here, so I can repli
Dave,
Exactly what I see unless I add c:/MinGW/bin to the windows system
Path (not PATH). cmake-gui fails, but the msys shell works fine.
Bill
On Fri, Jun 3, 2011 at 11:21 AM, David Cole wrote:
> On Fri, Jun 3, 2011 at 10:55 AM, Bill Hoffman
> wrote:
>> On 6/3/2011 8:10 AM, Bill Lorensen wrot
It makes a difference for me when running the cmake-gui. I have to
define a windows system Path not PATH. If I run from the msys shell,
everything is fine because the shell adds the proper path.
On Fri, Jun 3, 2011 at 11:23 AM, David Cole wrote:
> On Fri, Jun 3, 2011 at 8:10 AM, Bill Lorensen wr
if(argIsFile)
{
// Source CMakeLists.txt file given. It was probably dropped
// onto the executable in a GUI. Default to an in-source build.
this->SetHomeOutputDirectory(listPath.c_str());
this->SetStartOutputDirectory(listPath.c_str());
}
I'm too yo
On 6/3/2011 11:22 AM, Steve Westenbroek wrote:
Thanks Bill and Bill for looking into this!
I don't know if this was clear in my original post, but is seems that
most of my troubles with CMake on my system stem from the fact that I
have nearly half-a-dozen MinGW/MSYS installs on my system; each e
On Fri, Jun 3, 2011 at 8:10 AM, Bill Lorensen wrote:
> My version is 3.18 and I have to add c:/MinGW/bin to my windows Path
> otherwise the I get the missing dll error. I did not have to do this
> in earlier mingw versions. Notice I set it in Path and not PATH.
>
Path and PATH are equivalent vari
Thanks Bill and Bill for looking into this!
I don't know if this was clear in my original post, but is seems that
most of my troubles with CMake on my system stem from the fact that I
have nearly half-a-dozen MinGW/MSYS installs on my system; each exists
for a specific purpose, and each has it
On Fri, Jun 3, 2011 at 10:55 AM, Bill Hoffman wrote:
> On 6/3/2011 8:10 AM, Bill Lorensen wrote:
>>
>> My version is 3.18 and I have to add c:/MinGW/bin to my windows Path
>> otherwise the I get the missing dll error. I did not have to do this
>> in earlier mingw versions. Notice I set it in Path
On Fri, Jun 3, 2011 at 4:38 AM, NoRulez wrote:
> Is this the only way? Because i would like to have only one CTestScript.cmake
> file which came from the build server.
>
Of course it's not the only way. (TMTOWTDI: always, even if you're not
using perl.) It is a reasonable suggestion, though. It'
On Fri, Jun 3, 2011 at 9:10 AM, Eric Noulard wrote:
> 2011/6/3 Jean-Christophe Fillion-Robin :
>> Just tested it on linux and the same remark applies.
>
> Hi,
>
> I cannot find the answer in the ML archive but I think I already
> crossed that issue in the past
> and I was answered that this was th
Don't do it in your CMakeLists.txt file.
Do it in the script that drives your coverage build. If the script
runs on more than one machine, then add appropriate conditionals into
the script to handle the platform differences.
HTH,
David
On Fri, Jun 3, 2011 at 3:48 AM, Arunmozhi wrote:
> Hi,
>
>
On 6/3/2011 8:10 AM, Bill Lorensen wrote:
My version is 3.18 and I have to add c:/MinGW/bin to my windows Path
otherwise the I get the missing dll error. I did not have to do this
in earlier mingw versions. Notice I set it in Path and not PATH.
Strange, they must have changed the version schem
2011/6/3 NoRulez :
> Is this the only way? Because i would like to have only one CTestScript.cmake
> file which came from the build server.
I do not see the point?
If you use CPACK_PROJECT_CONFIG_FILE **in your project CMakeLists.txt**
then you'll get what you want with a single CTestScript.cma
2011/6/3 NoRulez :
> Is it possible to use a command such as ctest_*? because in my main
> CTestScript.cmake file it isn't possible to call add_test.
May be you can use
ctest_build(TARGET package)
this suppose the package target has been configure properly on the
particuler build server.
Note
2011/6/3 Jean-Christophe Fillion-Robin :
> Just tested it on linux and the same remark applies.
Hi,
I cannot find the answer in the ML archive but I think I already
crossed that issue in the past
and I was answered that this was the expected "legacy CMake" behavior.
1) When you specify a directo
My version is 3.18 and I have to add c:/MinGW/bin to my windows Path
otherwise the I get the missing dll error. I did not have to do this
in earlier mingw versions. Notice I set it in Path and not PATH.
Bill
On Thu, Jun 2, 2011 at 4:16 PM, Bill Hoffman wrote:
> On 6/2/2011 4:01 PM, Lecourt Maxim
Is this the only way? Because i would like to have only one CTestScript.cmake
file which came from the build server.
Am 01.06.2011 um 23:48 schrieb Clinton Stimpson :
> On Wednesday, June 01, 2011 02:58:22 pm NoRulez wrote:
>> Hi,
>>
>> if I use PackageMaker, DragNDrop, Bundle, OSXX11 then the
Is it possible to use a command such as ctest_*? because in my main
CTestScript.cmake file it isn't possible to call add_test.
Am 01.06.2011 um 23:11 schrieb Clinton Stimpson :
>
> On Wednesday, June 01, 2011 03:01:12 pm NoRulez wrote:
>> Hi,
>>
>> is it possible to also report CPack errors to
Hi,
I cannot understand how to include the flags -fprofile-arcs -ftest-coverage to
the compiler/linker flags or purify flags in my CMakeLists.txt. Why can't CTest
application and/or INCLUDE(CTest) itself do this automatically as it knows the
specific platform and coverage/memcheck tool used.
23 matches
Mail list logo
