During development, I don't expect INSTALL targets will be used at
all. The main reason I initially wanted this directory structure was
because I was planning to have a configuration file for each
application, and I thought I would name it "configuration".
However, if all the executables are
On Thu, Jan 29, 2009 at 9:47 PM, Tron Thomas wrote:
> The point about the PATH needed for DLL's under this directory structure is
> something I forgot to take into account when I was contemplating how to
> organize things. It would not work out well with what I had in mind. Given
> that, I think
The point about the PATH needed for DLL's under this directory structure
is something I forgot to take into account when I was contemplating how
to organize things. It would not work out well with what I had in
mind. Given that, I think I will have to consider a different strategy.
Philip Lo
On Tue, Jan 27, 2009 at 10:34 PM, Tron Thomas wrote:
> I want to use CMake to configure a project that will build several
> applications. I would like things such that each built program ends up in a
> directory path like:
> .../BuildDirectory/Debug/ApplicationName/AppliationName(.exe)
>
>
> What
On Wednesday 28 January 2009, Tron Thomas wrote:
> I want to use CMake to configure a project that will build several
> applications. I would like things such that each built program ends up
> in a directory path like:
> .../BuildDirectory/Debug/ApplicationName/AppliationName(.exe)
>
>
> What is n
I want to use CMake to configure a project that will build several
applications. I would like things such that each built program ends up
in a directory path like:
.../BuildDirectory/Debug/ApplicationName/AppliationName(.exe)
What is needed to cause CMake to configure this kind of build outpu
