uot;waterlooApps" which is not built by this project.
waterlooApps must be a declared target before calling TARGET_LINK_LIBRARIES()
ADD_EXECUTABLE(waterlooApps ${waterlooApps_SRCS})
TARGET_LINK_LIBRARIES(waterlooApps foo)
--
Cheers!
kitts
___
CMak
>>
> >> /usr/bin/c++ -I/foo/bar/32bit/include:/foo/bar/include ...
> >>
> >> instead of
> >>
> >> /usr/bin/c++ -I/foo/bar/32bit/include -I/foo/bar/include ...
What happens if you do not include the quotes?
INCLUDE_DIRECTORIES( $ENV{MY_SPECIAL_INC
does not offer all goodies such as code
completion, code navigation, documentation etc.
I didn't want to bring in an unintuitive directory structure to aid this.
Still confused! :-)
--
Cheers!
kitts
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
On Saturday 25 Aug 2007 12:33:02 am kitts wrote:
> On Friday 24 Aug 2007 11:43:12 pm kitts wrote:
> > On Friday 24 Aug 2007 9:41:26 pm James Bigler wrote:
> > > >> Code is organized as;
> > > >> src/common
> > > >> src/project1
> > >
On Friday 24 Aug 2007 11:43:12 pm kitts wrote:
> On Friday 24 Aug 2007 9:41:26 pm James Bigler wrote:
> > >> Code is organized as;
> > >> src/common
> > >> src/project1
> > >> src/project2
> > >>
> > >> The CMakeList
The other problem with the above approach is if there is a change in the
project variables, the common code is not updated. I would want to merge
common into the project in a way as though it were a subdirectory. Is this
possible?
--
Cheers!
kitts
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
On Thursday 23 Aug 2007 3:53:41 pm kitts wrote:
> Anyway, I have a new set of projects and my current problem is that i have
> some code that i share between projects. Once source can be shared not
> binaries.
>
> Code is organized as;
> src/common
> src/project1
&
ls good to be back! :-)
--
Cheers!
kitts
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
-.cmake file in Modules/Platform/ is
> needed for this.
> If you have the cmake files which have the build rule variables can you
> please post them ?
Sure i will arrange for this early next week. I am going on a vacation.
--
Cheers!
kitts
__
On Friday 15 Jun 2007 6:06:14 pm Alexander Neundorf wrote:
> Hi,
>
> On Friday 15 June 2007 02:54, kitts wrote:
> ...
>
> > I cannot publish the source but let me describe how i do it now with my
> > project at work.
> >
> > In the top level cmakelists.
.
The problem i foresee is that when you pass another library as a source file
to a library, cmake may not pass this file as an argument when building your
library.
--
Cheers!
kitts
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
f there is an issue in the way i organize the folders please do
suggest better options.
--
Cheers!
kitts
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
affect people.
Solving this might even solve the case of assembly files. At least with GCC
where GCC *can* assemble the file but its not passed as a file to the
compiler.
Is there a cmake variable to set/get the file extentions supported by the
compiler?
--
Cheers!
kitts
es
> completely unnoticed in cmake.html. Even if the FAQ remained external
> to the docs, a TOC would make it much easier to figure out where the
> FAQ is.
+1
--
Cheers!
kitts
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
should keep them quiet for sometime. Thanks for this simplified
solution. In which version can we expect this?
--
Cheers!
kitts
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
On Wednesday 23 May 2007 10:31:03 pm Alexander Neundorf wrote:
> > Yes. Its __ICCARM__ for ARM and __ICCAVR__ for AVR.
>
> Is there also a generic one without the architecture ?
There is __IAR_SYSTEMS_ICC__
--
Regards,
Kishore
___
CMake mailing list
CMa
On Wednesday 23 May 2007 9:36:56 pm Alexander Neundorf wrote:
> > OK. I recently added support for the IAR toolchain in my project. IAR is
> > quite different when compared to GCC variants that I had used until now.
> > IAR itself is available for multiple architectures and the difference is
> > on
X.cmake files, where
> several FIND_PATHs are used and all found paths then are
> combined in XXX_INCLUDE_DIRS. and it's ugly if both
> XXX_INCLUDE_DIRS and all the single paths appear in
> ccmake.)
When using the SET() function, mark the variable as "INTERNAL" and it will
html
Is it not possible to make target all depend on clean so that clean is run
before all?
> -Bill
--
Cheers!
kitts
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
On Monday 26 Mar 2007 at 11:08:07 pm, Filipe Sousa wrote:
> > What are variables where the information for each of the above is
> > stored? Especially for ADD_DEFINITIONS and INCLUDE_DIRECTORIES.
>
> GET_DIRECTORY_PROPERTY(defs DEFINITIONS)
> GET_DIRECTORY_PROPERTY(includes INCLUDE_DIRECTORIES)
I
Cheers!
kitts
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
On Friday 16 Mar 2007 IST, Brandon J. Van Every wrote:
> Kishore, Jonnalagadda (IE10) wrote:
> >> -Original Message-
> >>
> >>
> >> CMAKE_INCLUDE_CURRENT_DIR is the same as
> >> INCLUDE_DIRECTORIES(${CMAKE_CURRENT_BINARY_DIR}
> >> ${CMAKE_CURRENT_SOURCE_DIR}) for all targets.
> >>
> >>
On Thursday 01 Mar 2007 IST, Kishore, Jonnalagadda (IE10) wrote:
> I have recently tried porting a project to CMake but I am facing a few
> issues when cross-compiling
>
> The project can be compiled with a varying set of compilers (already
> works with our custom makefiles) and currently the only
On Monday 29 Jan 2007 IST, Alan W. Irwin wrote:
> On 2007-01-29 22:26+0530 kitts wrote:
> > # Here I would like SRC_LST to be updated inside the subdir, however,
> > # SRC_LST has the complete list in the subdir not changes made are
> > # lost as it returns to
On Monday 29 Jan 2007 IST, Radu Serban wrote:
> kitts wrote:
> > # Here I would like SRC_LST to be updated inside the subdir, however,
> > # SRC_LST has the complete list in the subdir not changes made are
> > # lost as it returns to this parent directory
> &
On Monday 29 Jan 2007 IST, kitts wrote:
> Is it possible to update a variable inside a subfolders CMakeLists.txt?
>
> It appears that the scope of the variable is limited to the current
> CMakeLists.txt but is possible to get the above behavior?
To explain a lil more:
I have the
Is it possible to update a variable inside a subfolders CMakeLists.txt?
It appears that the scope of the variable is limited to the current
CMakeLists.txt but is possible to get the above behavior?
--
Cheers!
kitts
___
CMake mailing list
CMake
On Wednesday 24 January 2007 02:15 IST, Claus Klein wrote:
> On Tuesday 23 January 2007 18:10, kitts wrote:
> > On Tuesday 23 January 2007 00:03 IST, kitts wrote:
> > > 2) On windows, we would like to use VS as the IDE and KDevelop on
> > > linux. Both are capable of cro
On Tuesday 23 January 2007 00:03 IST, kitts wrote:
> 2) On windows, we would like to use VS as the IDE and KDevelop on linux.
> Both are capable of crosscompiling (use non-native compilers). I think
> this is only possible by setting CMAKE_C_COMPILER to the compiler to use?
I tested t
that also. Here's one for your
> bookmarks:
> <http://www.cmake.org/Bug/query.php?op=query&form=advanced>
http://www.cmake.org/Bug/bug.php?op=show&bugid=1527&pos=2
http://www.cmake.org/Bug/bug.php?op=show&bugid=39
output did
help! :-P) and is now our default build system for all future work!
Thank you guys! :-)
--
Cheers!
kitts
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
>rosegarden/src/CMakeLists.txt
Thanks. But here we are referring to one static library linking to another.
The library being linked to could have been a convenience lib lust to avoid
multiple compilations.
--
Cheers!
kitts
___
CMake mailing list
CMake
arget lib but
that dint build them together either. The current target built itself like
it had no dependency on the common library.
--
Cheers!
kitts
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
o build the libraries and not the application. We support library
in many environments and hence need a build and test infrastructure for it.
--
Cheers!
kitts
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
gcc is unable to build a
simple executable! This is probably something to do with the fact that i
have multiple cygwin1.dll's. :-)
--
Cheers!
kitts
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
well. :-)
--
Cheers!
kitts
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
36 matches
Mail list logo