[cmake-developers] [vc12/idl] output directory problem

[David Cole]

If this change fixes the problem... then the problem must be that the
midl tool is being run from the wrong directory when it fails. Or that
midl is being run at the same time for two different projects both
trying to write output into the same directory simultaneously? (But
wouldn't this latter one *still* be a problem with this fix....?)

I hate mysteries.




On Mon, Feb 23, 2015 at 1:32 PM, Brad King <brad.king at kitware.com> wrote:
> On 02/21/2015 07:58 AM, Tim Blechmann wrote:
>> i'd love to provide a reduced test case, though i can only reproduce
>> this in a complex real-world buildsystem, with dozens of libraries and
>> some include_external_msproject / add_dependencies pairs ...
> [snip]
>> that said, i wonder: why would it be ok to use a relative path in the
>> generated project ... or, what would be the disadvantage of using an
>> absolute path?
>
> I don't think that is a problem.  I was just hoping to add a test case.
> At least the existing test case should not be regressed by the change.
> Applied:
>
>  VS: Specify absolute output directory for the Midl tool
>  http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0b54e836
>
> Thanks,
> -Brad
>
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake-developers