2009/12/7 Michael Jackson :
>
> Just thinking out loud .. What if CMake had a "built-in" facility to check a
> common internet location for new/updated modules like a lot of programs do
> now-and-days. This (in my mind) would allow for the deployment of "Official"
> CMake modules (or at least those
On Dec 7, 2009, at 3:37 PM, Eric Noulard wrote:
2009/12/7 Nicholas Yue :
Hi,
Does it make sense to separate out the development and deployment
of
"Modules" in CMake?
This kind of idea have already been raised on the ML.
May be you should dig the ML archive in order to collect past idea
2009/12/7 Nicholas Yue :
> Hi,
>
> Does it make sense to separate out the development and deployment of
> "Modules" in CMake?
This kind of idea have already been raised on the ML.
May be you should dig the ML archive in order to collect past ideas
in order to see past pro- and cons- the main ide
Hi,
Does it make sense to separate out the development and deployment of
"Modules" in CMake?
I see an advantage because Modules update are more frequent as more
packages are added compare to the release cycle of CMake itself.
Maybe there is an easier way? Environment variable to po
