Re: [CMake] Bug 2331: partial match on source groups

[Andrew Maclean]

 
I think it is fixed in the latest version of CMake in the CVS. Certainly for Visual Studio 2005 everything seems Ok in this respect.
 
 
Regards 
 
Andrew 

-- Forwarded message --From: [EMAIL PROTECTED]
To: Date: Wed, 24 May 2006 08:55:28 +0100Subject: [CMake] Bug 2331: partial match on source groupsI have tried to use CMake 2.4.2 and came across the bug described in
2331 which was assigned to Bill Hoffman more than a year ago:"If we have a source group X/Y and another source group Z/Y then fileswhich we intend to go into Z/Y will in fact go into X/Y and Z/Y is never
created even though Z exists."I tried emailing Bill but my message times out, so I was wondering ifanyone can look at this, as this problem prevents our use of CMake -basically we can't get the correct folder structure in Visual 
Studio.NET2003.Regards,MikeVisit our website at http://www.ubs.comThis message contains confidential information and is intended onlyfor the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Pleasenotify the sender immediately by e-mail if you have received thise-mail by mistake and delete this e-mail from your system.E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,arrive late or incomplete, or contain viruses.  The sender thereforedoes not accept liability for any errors or omissions in the contentsof this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  Thismessage is provided for informational purposes and should not beconstrued as a solicitation or offer to buy or sell any securities orrelated financial instruments.
-- ___Andrew J. P. MacleanCentre for Autonomous SystemsThe Rose Street Building J04The University of Sydney  2006  NSWAUSTRALIA
Ph: +61 2 9351 3283Fax: +61 2 9351 7474URL: http://www.cas.edu.au/___
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] Passing requirements to users

[James Mansion]

>There will probably be a way to set the *interface*
>include file search path separately from the
>*implementation* search path.  Then when a library is
>linked its interface include file search path can be 
>included during compilation of source files using the
>library.

Great - and hopefully not just a -I setting but also
arbitrary -D settings etc as well (possibly varying
according to the way the library was built).

James


___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Passing requirements to users

[Brad King]

James Mansion wrote:

I.e. there are modules for each library, and these modules
(should) define a standard set of variables whioch give you
the required information.


Thanks - but its not what I wanted to hear. :-(

It does load a lot of identical donkey-work onto every dependent
project.  In my case, also, its not so much modules like this
as libraries built within my own tree - it seems messy to define
the include paths in the root spec file as I do now.  Can't help
feeling that bjam is much better at this.


CMake propagates linker directories and libraries automatically, but not 
include directories.  The reason is that right now link libraries are 
per-target but include directories are per-directory.


We do have future plans to add this support but it will be more long 
term.  There will probably be a way to set the *interface* include file 
search path separately from the *implementation* search path.  Then when 
a library is linked its interface include file search path can be 
included during compilation of source files using the library.


-Brad
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] Convenience Libraries and Precompiled Headers

[James Mansion]

>Conv. libs are not (officially) supported by cmake. Just
>compile all source files into the resulting library. That's
>what we do for KDE.

Oh, tht's a shame.  I was hoping to be able to use a single
structure which would build static or dynamic libs as either
multiple small libraries or one big one, selectable, without
having any duplication of lists of sources etc.

James




___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

RE: [CMake] Passing requirements to users

[James Mansion]

>I.e. there are modules for each library, and these modules
>(should) define a standard set of variables whioch give you
>the required information.

Thanks - but its not what I wanted to hear. :-(

It does load a lot of identical donkey-work onto every dependent
project.  In my case, also, its not so much modules like this
as libraries built within my own tree - it seems messy to define
the include paths in the root spec file as I do now.  Can't help
feeling that bjam is much better at this.

I'll have to have a look at the guts of Cmake's generators
anyway.  I have in mind that there's no way to set the ANSI
compatibility flags for for-loop scopes, schar_t etc in VS2003
builds and I'd like to do that (the vcproj needs explicit flags,
rather than parsing the -D flags).  Maybe it will be obvious
what to do. ;-)


___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Makefile build progress support

[Filipe Sousa]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ken Martin wrote:
> I have added progress reporting to the makefile based builds. It is checked
> into CMake CVS and "should" work with any make and parallel builds. The
> percentage done is based on source file counts without knowing if the source
> files are up to date or not. Specifically the progress is not a good
> indicator of time left except for clean builds, it is an indicator of source
> files left to consider and possibly build, if that makes any sense :)
> Progress is supported for the top level all target and for all top level
> cmake executable/library targets. It has had limited testing so let me know
> if it fails etc.
> 
> Thanks
> Ken

It's ugly :( but that's my personal opinion

Building CXX object db/CMakeFiles/db.dir/transation.o
  1% complete
Linking CXX static library ../lib/libdb.a
  1% complete
Generating mainwindow.moc.cc
Generating databasedlg.moc.cc
Generating gal.qrc.cc
Scanning dependencies of target gal
Generating mainwindow.ui.h
Building CXX object app/CMakeFiles/gal.dir/main.o
  2% complete
Generating databasedlg.ui.h
Generating logindlg.ui.h
Building CXX object app/CMakeFiles/gal.dir/mainwindow.o
  3% complete
Building CXX object app/CMakeFiles/gal.dir/logindlg.o
  4% complete
Building CXX object app/CMakeFiles/gal.dir/databasemanagermodel.o
  5% complete
Building CXX object app/CMakeFiles/gal.dir/databasedlg.o
  6% complete
Building CXX object app/CMakeFiles/gal.dir/qsql_mysql.o
  7% complete
Building CXX object app/CMakeFiles/gal.dir/mainwindow.moc.o
  8% complete
Building CXX object app/CMakeFiles/gal.dir/databasedlg.moc.o
  9% complete
Building CXX object app/CMakeFiles/gal.dir/gal.qrc.o
 10% complete
Linking CXX executable ../bin/gal
 10% complete

Wouldn't be better if we put the percentage in the same line:

[ 8%] Building CXX object app/CMakeFiles/gal.dir/gal.qrc.o
[10%] Linking CXX executable ../bin/gal

- --
Filipe Sousa
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFEdJ7HbQdNYqwwwCwRAhapAJ0coO17Ul/RlDrAFbRtvz2XUKRBqACfZJf8
WmeL2R7N/ivFoTRE+2YnEQ0=
=oIbO
-END PGP SIGNATURE-
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

[CMake] Makefile build progress support

[Ken Martin]

I have added progress reporting to the makefile based builds. It is checked
into CMake CVS and "should" work with any make and parallel builds. The
percentage done is based on source file counts without knowing if the source
files are up to date or not. Specifically the progress is not a good
indicator of time left except for clean builds, it is an indicator of source
files left to consider and possibly build, if that makes any sense :)
Progress is supported for the top level all target and for all top level
cmake executable/library targets. It has had limited testing so let me know
if it fails etc.

Thanks
Ken

___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

[CMake] Bug 2331: partial match on source groups

[Michael . Rans]

I have tried to use CMake 2.4.2 and came across the bug described in
2331 which was assigned to Bill Hoffman more than a year ago:
"If we have a source group X/Y and another source group Z/Y then files
which we intend to go into Z/Y will in fact go into X/Y and Z/Y is never
created even though Z exists." 

I tried emailing Bill but my message times out, so I was wondering if
anyone can look at this, as this problem prevents our use of CMake -
basically we can't get the correct folder structure in Visual Studio.NET
2003. 

Regards,
Mike


Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.

___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Add non-build files to a project?

[Jan Woetzel]

Jan Woetzel wrote:

ADD_EXECUTABLE(dummy dummy.cpp 
"${CMAKE_CURRENT_BINARY_DIR}/Doc/index.html")


Sidenote:
I think you have to take care that they are added only to VS IDE 
generator builds,

in particular NOT to makefiles.

Thus we are using something like this:

IF(CMAKE_BUILD_TOOL MATCHES "(msdev|devenv)")
ADD_EXECUTABLE( hello ${SOURCES} ${HEADER} ${DOC})
ELSE  (CMAKE_BUILD_TOOL MATCHES "(msdev|devenv)")
 ADD_EXECUTABLE( hello ${SOURCES} )
ENDIF (CMAKE_BUILD_TOOL MATCHES "(msdev|devenv)")

Jan.

--

 Dipl.-Ing. Jan Woetzel
--
 University of Kiel
 Institute of Computer Science and Applied Mathematics
 Hermann-Rodewald-Str. 3 [room 310]
 24098 Kiel/Germany
--
 Phone +49-431-880-4477
 Fax   +49-431-880-4054
 Mob.  +49-179-2937346
--
 Url   www.mip.informatik.uni-kiel.de/~jw
 Email [EMAIL PROTECTED]

___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Add non-build files to a project?

[Jan Woetzel]

James Mansion wrote:


VStudio projects I add in the includes and
the documentation text and web files so I can
select them easily for editing.
 

You could add arbitray files to a target - as long as VS has no 
"automatic" rule to compile them (e.g. .cc, .cpp etc)

I am adding .html files to libraries/executable or using a dummy target e.g:

ADD_EXECUTABLE(dummy dummy.cpp 
"${CMAKE_CURRENT_BINARY_DIR}/Doc/index.html")


SOURCE_GROUP command may be useful, too.

Jan.

--

 Dipl.-Ing. Jan Woetzel
--
 University of Kiel
 Institute of Computer Science and Applied Mathematics
 Hermann-Rodewald-Str. 3 [room 310]
 24098 Kiel/Germany
--
 Phone +49-431-880-4477
 Fax   +49-431-880-4054
 Mob.  +49-179-2937346
--
 Url   www.mip.informatik.uni-kiel.de/~jw
 Email [EMAIL PROTECTED]

___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake