On Tuesday 29 Nov 2011 10:50:13 AM Mathias Gaunard wrote:
> On 11/28/2011 05:58 PM, Kishore Jonnalagadda wrote:
> > I have recently moved to using 64bit Kubuntu Oneiric when supports
> > multiarch. I understand that building 32 bit from my 64 install is as
> > simple as adding
ke to look for 32bit libs?
--
Cheers!
Kishore
Ps: Is this "multiarch" unique to *ubuntu or all distributions adopting it?
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the
ic package
file.
--
Cheers!
Kishore>From 648977fbc8e0d22692f125fb4ed9fe6cc015b430 Mon Sep 17 00:00:00 2001
From: Kishore Jonnalagadda
Date: Thu, 10 Nov 2011 20:18:06 +0530
Subject: [PATCH] Even through the file name has "Unpecified" in it, let the
control file and thus the installed pac
On Sat, Sep 17, 2011 at 2:12 PM, Eric Noulard wrote:
> 2011/9/17 Kishore Jonnalagadda :
>> In my project I am using the default component for all binaries and a "dev"
>> component for headers.
>>
>> But when I create packages, it creates one called "Unsp
On Sep 17, 2011 2:12 PM, "Eric Noulard" wrote:
>
> 2011/9/17 Kishore Jonnalagadda :
> > In my project I am using the default component for all binaries and a
"dev"
> > component for headers.
> >
> > But when I create packages, it creates one calle
b and myproj-dev.deb?
--
Cheers!
Kishore
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_F
xpect... I expected a link to the page
http://www.cmake.org/cmake/help/documentation.html which I got from a google
search.
> On Tue, Jun 21, 2011 at 1:55 PM, Kishore Jonnalagadda <
kitts.mailingli...@gmail.com> wrote:
>>
>> Should not the cmake help web page (
http://www.cmake.or
Should not the cmake help web page (
http://www.cmake.org/cmake/help/help.html) contain a link to the
documentation page?
--
Cheers,
Kishore
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource
CMAKE_C_FLAGS})
>
> SET (CMAKE_C_CREATE_STATIC_LIBRARY " --create -cr
> ") SET (CMAKE_CXX_CREATE_STATIC_LIBRARY "
> --create -cr ")
>
> INCLUDE_DIRECTORIES(${RVCT40INC})
> LINK_DIRECTORIES(${RVCT40LIB}/armlib ${RVCT40LIB}/cpplib)
> ADD_EXECUTABL
xt (either before or
after PROJECT()) does no good.
Placing the code just before the PROJECT() call causes it to be overwritten to
include just "c" when checked after PROJECT() call. This whole thing is very
confusing and some documentation would help.
--
Cheers!
Kishore
_
dded systems. In addition, I
would also like the scope of the three platform/* modules to be documented as
well.
--
Cheers!
Kishore
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.
current dir.
> ... rather than
> cd /some/source/dir ; cmake /some/build/dir
Reversed paths! :P
--
Cheers!
Kishore
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
P
On Sunday 05 Dec 2010 6:16:35 pm Michael Hertling wrote:
> On 11/30/2010 05:53 AM, Kishore wrote:
> > On Tuesday 23 Nov 2010 5:27:56 pm Johannes Zarl wrote:
> >> Another somehow related topic seems to be import/export of targets. Should
> >> a LibraryConfig.cmake or Fi
> And is there any documentation on how to create a LibraryConfig.cmake file
> with support for components?
--
Cheers!
Kishore
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.ht
t include_directories(mylib/h) into the top-level CMakeLists.txt.
>
> naturally but include_directories() in top-level cmakelists.txt is quite
> hard to maintance for live project with few levels of hierarchy and
> hundreds
> of sh
ck to allow for that? Do we need something like
> that?
> I've been getting along fine for a while and I just edit the cmake files
> of my subprojects.
> I don't know about others though.
The way i see this... Project A's "Devel" component is made to depend on
On Friday 06 Aug 2010 4:18:36 am Eric Noulard wrote:
> 2010/8/4 Kishore :
> > On Monday 02 Aug 2010 4:59:47 pm Eric Noulard wrote:
> >> Hi All,
> >>
> >> I did add a patch for the "multiple file problem"
> >> http://public.kitware.com/Bug/vi
ack generators (but the archive one) behaves as before
> with either componentized project or not.
>
> Waiting for feedback before going on
Thanks. It just tried this and it works as claimed. Later today, i will
inspect the generated packages on a windows machine too.
--
Cheers!
Kishore
ecause then you would get a multiple definition error. Since the same file is
compiled and linked twice effectively. Once when included from main.cpp and the
other when passed as a separate file to the compiler/linker.
--
Cheers!
Kishore
___
Powered by ww
M. For the more advanced, like dependency between
components, i would first need to check the level of support in NSIS.
Nevertheless, DEB and RPM can benefit from inter component dependencies.
>
> Thanks,
> David
>
> On Fri, Jul 30, 2010 at 1:02 AM, Kishore
wrote:
> > I w
On Friday 30 Jul 2010 5:05:56 pm Eric Noulard wrote:
> Hi All,
> I'll try to launch a specific thread for this following what
>
> Kishore said:
> > I would like to see full support for multiple components in cpack.
>
> David answered:
> > Could you elab
n
> the bug tracker that you are interested in seeing fixed for 2.8.3 -- we
> will be looking at the mailing list and activity in the bug tracker to
> help prioritize the bug fixes that will occur in the next several weeks.
>
>
> Thanks,
> David Cole
> Kitware, Inc.
-
On Wednesday 28 Jul 2010 10:01:42 pm Eric Noulard wrote:
> 2010/7/28 Kishore :
> >> bash-completion 1:1.2-2
> >
> > bash-completion 1:1.1-3ubuntu2
>
> I think I know why. The missing functions may comes with bash-completion
> 1.2 you have 1.1.
>
>
On Wednesday 28 Jul 2010 7:07:20 pm Eric Noulard wrote:
> 2010/7/28 Kishore :
> > On Tuesday 27 Jul 2010 6:05:59 pm Eric Noulard wrote:
> >> 2010/7/27 Eric Noulard :
> >> > Here comes a proposal for a bash completion for cmake. Should work
> >> > with a
completion project:
> https://alioth.debian.org/tracker/index.php?func=detail&aid=312632&group_id
> =100114&atid=413095
Thanks a lot for this. Unfortunately it does not work here. This is what i get
with "cmake "
$ cmake _get_comp_words_by_ref: command not found
-_get_com
On Wednesday 07 Jul 2010 8:54:52 pm Kishore wrote:
> On Friday 02 Jul 2010 12:36:17 am Kishore wrote:
> > On Friday 02 Jul 2010 12:07:07 am Alexander Neundorf wrote:
> > > On Thursday 01 July 2010, Kishore wrote:
> > > > It seems that the PROJECT() command doe
On Friday 02 Jul 2010 12:36:17 am Kishore wrote:
> On Friday 02 Jul 2010 12:07:07 am Alexander Neundorf wrote:
> > On Thursday 01 July 2010, Kishore wrote:
> > > It seems that the PROJECT() command does a fair bit behind the scenes
> > > and is not documented enough.
On Thursday 01 Jul 2010 8:13:56 pm Kishore wrote:
> In the CMake wiki (http://www.cmake.org/Wiki/CMake_Cross_Compiling) it says
> clearly that the platform module are included in the following order;
>
> Platform/${CMAKE_SYSTEM_NAME}.cmake (mandatory)
> Platform/${CMAKE_SYST
On Friday 02 Jul 2010 12:07:07 am Alexander Neundorf wrote:
> On Thursday 01 July 2010, Kishore wrote:
> > It seems that the PROJECT() command does a fair bit behind the scenes and
> > is not documented enough. It seems to "reset" several variable created
>
rue on the first run of cmake and hence executing "make
rebuild_cache" overcomes the issue. Bug?
--
Cheers!
Kishore
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Ple
!
Kishore
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to
On Wednesday 16 Jun 2010 8:51:27 am you wrote:
> On Tuesday 15 Jun 2010 11:32:17 pm Andreas Pakulat wrote:
> > On 15.06.10 22:18:04, Kishore wrote:
> > > How do i inform cmake when building a module that it depends on another
> > > module? Does cmake need to even k
On Tuesday 15 Jun 2010 11:32:17 pm Andreas Pakulat wrote:
> On 15.06.10 22:18:04, Kishore wrote:
> > How do i inform cmake when building a module that it depends on another
> > module? Does cmake need to even know that?
> >
> > I am building a plugin based qt appl
!
Kishore
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to
You cannot move a configured project. If you move it you need to clean
the build folder and then run cmake again after the move.
Warm regards,
Kishore
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of abhijeet mhatre
Sent: Thursday, June 07
them would
tend to have that amount of knowledge. Of course for ease with commonly
used processors, the CMAKE_SYSTEM_PROCESSOR could also be used!
Regards,
Kishore
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Alexander Neundorf
> Sent: Wednesday, May 23, 2007 6:00 PM
> To: cmake@cmake.org
> Subject: Re: [CMake] [Dev] CMake 2.5-20070519 and tool chain support
>
> On Wednesday
> On Tuesday 22 May 2007 10:32, Kishore, Jonnalagadda (IE10) wrote:
> ...
> > It would make it very easy for one to distribute the project with
the
> > respective cmake support files when cmake officially does not
support
> > the configuration. Or if the for some reason one want
officially does not support
the configuration. Or if the for some reason one wants to override the
default configuration.
Warm regards,
Kishore
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Trevor Kellaway
> Sent: Friday, May 11, 2007 12:15 AM
> To: cmake@cmake.org
> Subject: RE: [CMake] RE: CMake 2.4.1/VC71 Why the wierd .dir
> subdirs?
>
> Kishore
re are a way of recovering the current include and define
> lists?
Perhaps you could use GET_DIRECTORY_PROPERTY()?
GET_DIRECTORY_PROPERTY(INC_LIST INCLUDE_DIRECTORIES)
GET_DIRECTORY_PROPERTY(DEFS DEFINITIONS)
Regards,
Kishore
___
CMake mailing list
CMa
commands.
`nmake VERBOSE=1` should give a verbose enough output. This works with
make... not sure about nmake.
Regards,
Kishore
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Trevor Kellaway
> Sent: Saturday, May 05, 2007 1:49 PM
> To: cmake@cmake.org
> Subject: RE: [CMake] Thoughts on Cross-compiling with CMake
>
> Kishore,
>
> > O
st hand experience
with this kind of use. In past discussions, I learnt that it is possible
to use the GCC compiler when building from VS. The downside being that
error parsing won't work. So no click-on-error-message to show the
relevant source lines.
Regards,
Kishore
l
studio (and may be eclipse) project with the cross-compiler settings.
This is probably not a problem for KDevelop as it is just a front end to
other command line tools.
I can contribute in testing. My setup requires me to work with several
processors and multiple compilers for each architecture.
OMPILER special in that they cannot be changed. To use another
compiler, set the environment variables for CC and CXX before calling
cmake for the very first time. See
http://www.cmake.org/Wiki/CMake_Useful_Variables#Compilers_and_Tools
Regards,
Kishore
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
ings ?
Place the variables in CACHE. You could try:
SET(utils_SRCS a.cpp b.cpp CACHE INTERNAL "" FORCE)
Warm regards,
Kishore
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
MPILE_FLAGS}
${PLATFORM_CXX_FLAGS}" CACHE STRING "" FORCE)
ELSEIF(${TOOLCHAIN} STREQUAL "METROWERKS")
MESSAGE(FATAL_ERROR "The toolchain METROWERKS is not supported
for the m68k architecture.
Supported toolchains are GCC.")
ENDIF(${TOOLCHAIN} STREQUAL "GCC")
Warm regards,
Kishore
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Sorry. I observed more closely with VERBOSE=1. It is not cmake's fault.
Cmake passes the argument "as is" but when the compiler returns an
error; it replaces the leading -- with -f in the error message.
Warm regards,
Kishore
> -Original Message-
> From: Bill H
If I add the flag "--register-prefix-optional" cmake actually passes
"-fregister-prefix-optional" to the command line and this causes the
command to fail saying that the option does not exist.
How can I avoid this?
Warm regards,
Kishore
_
> Kishore, Jonnalagadda (IE10) wrote:
> >> KJI> This would have worked just fine except that
INCLUDE_DIRECTORIES
> >> returns
> >> KJI> semicolon separated list of directory names not a space
separated
> >> list
> >>
> >> Seems
g the
definitions. I do not have a clear idea of the pattern in which the
backslashes are introduced.
Warm regards,
Kishore
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
> > Kishore, Jonnalagadda (IE10) wrote:
> > > Is there a variable with all the compile options concatenated? A
> > > variable with common CMAKE_C_FLAGS +
> CMAKE_C_FLAGS_${CMAKE_BUILD_TYPE} +
> > > ADD_DEFINITIONS() + INCLUDE_DIRECTORIES?
> > >
> &
> Kishore, Jonnalagadda (IE10) wrote:
> > Is there a variable with all the compile options concatenated? A
> > variable with common CMAKE_C_FLAGS +
CMAKE_C_FLAGS_${CMAKE_BUILD_TYPE} +
> > ADD_DEFINITIONS() + INCLUDE_DIRECTORIES?
> >
> >
> >
> >
mpiler or it won't take effect.
Warm regards,
Kishore
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
variables where the information for each of the above is
stored? Especially for ADD_DEFINITIONS and INCLUDE_DIRECTORIES.
Warm regards,
Kishore
Honeywell *
Honeywell Technology Solutions Lab (HTSL)
Doraisanipalya, Bannerghatta Road
Bangalore
INDIA
Ph: +91 (80) 26588360 (O), +919845140597 (M
irst option is in IMHO a better option in most cases.
Warm regards,
Kishore
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
laced after
declaring the project. If it is put before, then it gets overwritten
when project is declared. Can any of the developers throw more light on
the various effects that declaring a project has?
2) When cross-compiling, the CMAKE_C_COMPILER and CMAKE_CXX_COMPILER
must be set *before* dec
> Filipe Sousa wrote:
> > Kishore, Jonnalagadda (IE10) wrote:
> >> Is it possible to set the prefix and suffix to "lib" and ".a" for
all
> >> libraries and ".elf" suffix to all executables?
> >
> > CMAKE_STATIC_LIBRARY_P
propogated and cmake complains that it cannot find the .o files but has
searched with various extension like .c .C .cxx ...
Is there a solution for this? Besides, is there a cleaner solution for
assembling? For example can I declare a custom command for processing
any files that have a .S extension and then simple pass the assembly
source files to a target and let cmake automatically call the custom
command on these files?
Warm regards,
Kishore
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Is it possible to set the prefix and suffix to "lib" and ".a" for all
libraries and ".elf" suffix to all executables?
As mentioned in an earlier mail, I am having trouble with the executable
trying to link to libraries with .lib
ried this before? I have read a couple of entries in
the archives from which I derived the above but they are either too old
or do not work.
Can anyone help?
Warm regards,
Kishore
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Kishore, Jonnalagadda (IE10)
> Sent: Wednesday, March 21, 2007 1:28 AM
> To: cmake@cmake.org
> Subject: [CMake] LINK_LIBRARIES() does not respect SUFFIX/PREFIX
>
ry file in the build directory.
How do I solve this problem? Why is the .lib being appended in the call
to the linker?
Warm regards,
Kishore
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
S SRC_LIST)
I get the MESSAGE prints but not the echo output. Seems like custom
command is not executed?! What is wrong here?
Warm regards,
Kishore
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
hat is the
role/purpose of those variables?
Warm regards,
Kishore
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
. Is there a wiki or a tutorial
on this?
Warm regards,
Kishore
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
ault "x86".
How can I control this?
Warm regards,
Kishore
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
> On Tuesday 20 March 2007 07:07:35 Kishore, Jonnalagadda (IE10) wrote:
> > > Kishore, Jonnalagadda (IE10) wrote:
> > This is now a little confusing especially, when the description says
"
> > automatically add CMAKE_CURRENT_SOURCE_DIR and
CMAKE_CURRENT_BINARY_DIR
&
> Kishore, Jonnalagadda (IE10) wrote:
> >
> > If I understand you correctly, you mean to say that in the top level
> > CMakeLists.txt, if I SET(CMAKE_INCLUDE_CURRENT_DIR ON) and
> > INCLUDE_DIRECTORY(.) then all other subdirectories I add will all
> > automatica
> On Friday 16 March 2007 17:56:46 Brandon J. Van Every wrote:
> > Kishore, Jonnalagadda (IE10) wrote:
> > > But then, despite setting the value I had to put in
> > > INCLUDE_DIRECTORIES(.)
> >
> > And I was brief because I don't know if there any c
one of the pages... ;-)
I just checked again and confirm that the information was already there under
the section "Various Options"
http://www.cmake.org/Wiki/CMake_Useful_Variables#Various_Options
Now it is also added under "Environment Variables"
http://www.cmake
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Filipe Sousa
> Sent: Friday, March 16, 2007 2:33 AM
> To: cmake@cmake.org
> Subject: Re: [CMake] CMAKE_INCLUDE_CURRENT_DIR?
>
> -BEGIN PGP SIGNED MESSAGE
/CMake_Useful_Variables was that all the sub
directories included with the command ADD_SUBDIRECTORY() get included as
part of include directories for include files located elsewhere.
Warm regards,
Kishore
Ps. I am making progress with cross-compiling by forcing the TEST
variables as successful. I will
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Trevor Kellaway
Sent: Sunday, March 04, 2007 10:39 PM
To: kitts; cmake@cmake.org
Subject: RE: [CMake] crosscompiling problems on XP
>Kishore,
>> On Thursday 01 Mar 2007 IST, Kishore, Jonnalaga
thing on a Linux box where it works as
expected. Cmake passes when I do not issue '-G "Unix Makefiles"' but then the
compiler used is cl and not the intended avr-gcc. For various reasons, I cannot
use the Linux box for the build.
What is the solution to this?
Warm regar
76 matches
Mail list logo
