Am Samstag, 4. Juni 2011, 21:17:49 schrieb Stephen Kelly:
> Hi,
>
> I came up with an idea to simplify the creation of export headers for
> hidden visibility by using configure_file.
>
> After implementing it I saw that the idea has come up before :)
>
> http://www.mail-archive.com/cmake@cmake.o
>What kind of environment is this ?
>So you do this under windows, but with some kind of unix tools ?
>Is this cygwin or more like mingw ?
WindRiver provides the wrenv.exe/.sh (depending on the platform) utility to
help setup the environment for production. It is available for windows and unix
s
On Saturday, June 04, 2011 09:57:44 PM dfurt...@cox.net wrote:
> Usually we use the vxworks command shell to do command line builds.
> Windriver supplys many utilites including its own sh.exe. Is there a way
> to tell CMake to use the windriver sh and/or env setup?
Please keep the mailing list on
Hi,
I came up with an idea to simplify the creation of export headers for hidden
visibility by using configure_file.
After implementing it I saw that the idea has come up before :)
http://www.mail-archive.com/cmake@cmake.org/msg27058.html
Please see the attached proof of concept. Could we get
On Saturday, June 04, 2011 05:09:27 PM Dan Furtney wrote:
> Can the pre-link commands be added to the vxworks.cmake with a
> ADD_CUSTOM_COMMAND call? I initially tried doing this in the
> CMakeLists.txt file via a ADD_CUSTOM_COMMAND(TARGET...) call and a special
> LINK command I can't recall.
So
I'd like to know the same. Particularly with respect to whether any
documents will need to be signed, and for how much longer patches
(that aren't bug fixes) will be accepted to 2.8.5.
Thanks,
Steven
On Sat, Jun 4, 2011 at 1:53 AM, J Decker wrote:
> so what is the proper way for someone without
