[cmake-developers] GenerateExportHeader macro in CMake?

[David Cole]

Stephen,

Welcome to CMake development.... :-)

Brad and I are both fairly busy this week. Please continue making fixes and
merging them into 'next' for dashboard testing as you are able. You're
getting closer.

It looks like you already made a similar change to what Bill was asking us
to push...?

Let me know if you would like me to try anything on a specific machine here
at Kitware for you. I have access to all the Kitware dashboard machines, and
even some of the non-Kitware dashboard machines.

Thanks for your effort... We've all been there when adding something brand
new into CMake.

Keep up the good work!


David Cole
Kitware, Inc.


On Wed, Aug 10, 2011 at 5:21 PM, Bill Hoffman <bill.hoffman at kitware.com>wrote:

> I worked with Stephen today on this and it needs to put all the dll's in
> the same place as the main executable.
>
> The following makes the test pass on my windows box:
>
> diff --git a/Tests/Module/**GenerateExportHeader/**CMakeLists.txt
> b/Tests/Module/GenerateExportH
> index 6374087..0f5d792 100644
> --- a/Tests/Module/**GenerateExportHeader/**CMakeLists.txt
> +++ b/Tests/Module/**GenerateExportHeader/**CMakeLists.txt
> @@ -40,6 +40,8 @@ macro(_do_build Include Library LibrarySource Source)
>
>     "set(CMAKE_INCLUDE_CURRENT_DIR ON)\n"
>
> +    "set(CMAKE_RUNTIME_OUTPUT_**DIRECTORY \"${GenerateExportHeader_**
> BINARY_DIR}\")\n"
> +
>     "include(GenerateExportHeader)**\n"
>
>     "add_compiler_export_flags()\**n"
>
>
> Can you or Brad push this to the branch?
>
> -Bill
>
>
>
> On 8/10/2011 1:58 PM, David Cole wrote:
>
>> Stephen,
>>
>> The test you recently added is failing on many platforms on the CMake
>> dashboard today. Are you working on resolving these test failures?
>>
>> This output:
>>
>> *** Exception executing: Exit code 0xc0000135
>>
>> means that one of the dlls could not be loaded properly by the built
>> executable. Are you putting the dlls in the same directory with the
>> executables by setting CMAKE_RUNTIME_OUTPUT_DIR ... ?
>>
>> Do you have a Windows machine with Visual Studio on it for local testing?
>>
>>
>> Thanks,
>> David
>>
>>
>> On Tue, Aug 2, 2011 at 9:38 AM, Brad King <brad.king at kitware.com
>> <mailto:brad.king at kitware.com>**> wrote:
>>
>>    On 8/2/2011 3:40 AM, Stephen Kelly wrote:
>>
>>        Brad King wrote:
>>        I've now also tested with MSVC and MinGW on Windows. I couldn't
>>        seem to get
>>        cmake to work on cygwin though.
>>
>>        I'll see if I can test on Mac too before pushing to the cmake repo.
>>
>>        One question I have is: Will the unit tests for this be run on
>>        all platforms
>>        before it gets to master?
>>
>>
>>    Yes.  You will create a topic branch starting from 'master' but it will
>>    initially be merged into 'next' for testing.  If there are failures you
>>    will be able to extend the topic with corresponding fixes.  Only after
>>    the whole topic is mature will upstream developers merge it to
>> 'master'.
>>
>>    Thanks,
>>    -Brad
>>
>>    ______________________________**___________________
>>    cmake-developers mailing list
>>    cmake-developers at cmake.org <mailto:cmake-developers@**cmake.org<cmake-developers at cmake.org>
>> >
>>
>>    http://public.kitware.com/cgi-**__bin/mailman/listinfo/cmake-_**
>> _developers<http://public.kitware.com/cgi-__bin/mailman/listinfo/cmake-__developers>
>>    <http://public.kitware.com/**cgi-bin/mailman/listinfo/**
>> cmake-developers<http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers>
>> >
>>
>>
>>
>>
>> ______________________________**_________________
>> cmake-developers mailing list
>> cmake-developers at cmake.org
>> http://public.kitware.com/cgi-**bin/mailman/listinfo/cmake-**developers<http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers>
>>
>
>
> --
> Bill Hoffman
> Kitware, Inc.
> 28 Corporate Drive
> Clifton Park, NY 12065
> bill.hoffman at kitware.com
> http://www.kitware.com
> 518 881-4905 (Direct)
> 518 371-3971 x105
> Fax (518) 371-4573
>
> ______________________________**_________________
> cmake-developers mailing list
> cmake-developers at cmake.org
> http://public.kitware.com/cgi-**bin/mailman/listinfo/cmake-**developers<http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20110811/d5138ac5/attachment.html>