Hi.
I'm trying to compile .cpp file along with .asm on Visual Studio.
It correctly finds NASM assembler, but .asm file seems not to be included to
build.
Have tried VS 2005 and 2010, cmake 2.8.6 and 2.8.6-20111015.
It works on linux/make generators of course.
--
Best Regards,
Vladimir.
--
Pow
On 18.10.11 00:25:00, Claudio Bantaloukas wrote:
> Hi *
> I have installed the windows developer preview with visual studio 2011.
> I tried to use cmake 2.8.6 to generate a project but:
> - when I try to open the sln file, I get a modal dialog saying that the
> format is not recognized
> (in fact t
Hi *
I have installed the windows developer preview with visual studio 2011.
I tried to use cmake 2.8.6 to generate a project but:
- when I try to open the sln file, I get a modal dialog saying that the
format is not recognized
(in fact the .sln file can be opened if I change the header to
--
Micro
For now, a wrapper script is definitely the way to do this.
We need the ability to specify environment values generically in the
"add_custom_command" command. Once we have that, adding support to
ExternalProject will be trivial. Until we have that, a wrapper script
work-around is valid now and wil
Thanks Luigi. I feared a workaround was necessary. I will go over your
suggestion and try to apply it.
I'll second your suggestion for providing environment variables for
ExternalProjects.
Miki.
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/op
I'm still trying to figure this one out. I went in an unset _libdir and
manually set it to include the mkl path (even though it is the first thing on
the LD_LIBRARY_PATH) and it still can't find it. In other words,
set(_libdir /usr/local/lib /usr/lib /usr/local/lib64 /usr/lib64
/opt/intel/Comp
You could approach it in a different way:
Rather than having the end user running ctest control what tests are
run with -I or -R, you could have them provide a file that lists the
tests to run. Then you could construct the list from that file, run
only the configure/build steps that are necessary,
On 17/10/2011 18.27, Milutin Jovanovic' wrote:
Hi all,
Hi all. First time posting. Before I start I'd like to thank all the
Kitware guys for a very nice and useful tool. I did a fair bit of
searching to try to avoid asking duplicate questions, but did not find
answer to my problem.
I am tr
Hi all,
Hi all. First time posting. Before I start I'd like to thank all the Kitware
guys for a very nice and useful tool. I did a fair bit of searching to try
to avoid asking duplicate questions, but did not find answer to my problem.
I am trying to make a private build of some dependencies, ogg
Yes, we're writing the CTestTestfile.cmake with all of the available tests
using add_test(). So it sounds like there is no way to only configure/build
selected tests when using CTest outside of CMake, short of hand-writing the
CTestTestfile with only the desired tests.
I was going to suggest h
On Mon, Oct 17, 2011 at 11:04 AM, Tim Gallagher
wrote:
> Hi,
>
> Sorry I wasn't clearer. That section was from a script that we call with
> ctest. The entire section that runs things looks like
>
> # Load our custom settings
> ctest_read_custom_files("${CTEST_REPO_DIRECTORY}")
> ctest_start("Nigh
Hi,
Sorry I wasn't clearer. That section was from a script that we call with ctest.
The entire section that runs things looks like
# Load our custom settings
ctest_read_custom_files("${CTEST_REPO_DIR
On 10/17/2011 01:58 PM, Michael Hertling wrote:
> On 10/16/2011 06:27 PM, zex spectrum wrote:
>> Hello,
>>
>> I generate a shared library named, for example, mylib80.dll (it has
>> postfix "80", because I want to embed version info into library name.
>> I use set_target_properties with _POSTFIX pro
On 10/16/2011 06:27 PM, zex spectrum wrote:
> Hello,
>
> I generate a shared library named, for example, mylib80.dll (it has
> postfix "80", because I want to embed version info into library name.
> I use set_target_properties with _POSTFIX property to achieve
> this. By default, CMake names corre
> Hi,
>
> We're having problems with FindLAPACK in the latest source head. It claims
> it cannot find LAPACK when previous versions of CMake find it just fine.
> It does not work with either the Generic version or the Intel version.
> FindBLAS correctly locates the library though.
No idea so far.
2011/10/17 Tim Gallagher :
> Hi,
>
> We have our project set up to run a series of test cases, but we are treating
> it as if we are not using CMake. I found a tutorial online on how to set it
> up, and we have it running just fine when we want to run all of the tests.
> But, I haven't figured o
16 matches
Mail list logo