Quantcast

ZERO_CHECK generation and Xcode

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

ZERO_CHECK generation and Xcode

Steven Velez
If I understand correctly the purpose of the ZERO_CHECK target is to update the generated project files when necessary.

That's fine, but I have noticed on Xcode (8.2) that when ZERO_CHECK runs and updates the project, it causes the xcode build to abort.  Unfortunately, it seems this build abort happens before the xcode project regeneration has a chance to complete and update/touch CMakeFiles/cmake.check_cache, so once the target is out of date, it pretty much stays that way, and the builds are always (or least frequently) subsequently aborted because of an update to generated project files.

If I go in to the terminal and manually execute "make -f ReRunCMake.make" then the process completes and the ZERO_CHECK target is good, and it does not run any more.

Is there any known way to deal with this other than by specifying CMAKE_SUPRRESS_REGENERATION:BOOL=YES ?

Thanks,
Steven

--

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
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ZERO_CHECK generation and Xcode

CMake mailing list
Hi Steven,

On 3/29/17 5:24 PM, Steven Velez wrote:

> If I understand correctly the purpose of the ZERO_CHECK target is to update
> the generated project files when necessary.
>
> That's fine, but I have noticed on Xcode (8.2) that when ZERO_CHECK runs
> and updates the project, it causes the xcode build to abort.
> Unfortunately, it seems this build abort happens before the xcode project
> regeneration has a chance to complete and update/touch
> CMakeFiles/cmake.check_cache, so once the target is out of date, it pretty
> much stays that way, and the builds are always (or least frequently)
> subsequently aborted because of an update to generated project files.
>
> If I go in to the terminal and manually execute "make -f ReRunCMake.make"
> then the process completes and the ZERO_CHECK target is good, and it does
> not run any more.
>
> Is there any known way to deal with this other than by specifying
> CMAKE_SUPRRESS_REGENERATION:BOOL=YES ?

Could you please file a bug about this? I'll take a look during the 3.9
development cycle. Do you have a rather large or small project?

Thanks,
Gregor

--

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
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: ZERO_CHECK generation and Xcode

CMake mailing list
On 3/29/17 10:15 PM, Steven Velez wrote:
> I do have a pretty large project with around 142 targets.
>
> Another characteristic of note, and which I noticed while investigating
> this is that our project suffers from
> https://gitlab.kitware.com/cmake/cmake/issues/14297, and I think it is
> because we have "project" declarations underneath the top-level... so
> ZERO_CHECK builds concurrently with other targets.

Oh boy. Thanks for pointing this out.

> I did create an xcode scheme that builds a smaller set of targets (6), and
> made sure that they all depended on ZERO_CHECK, and then ZERO_CHECK ran by
> itself, and it appeared that after a single test, it did manage to complete
> updating so that it did not run on subsequent invocations.

I'll have a look.
--

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
Loading...