Re: internal lib name vs. output lib name, getting internal dependencies?

2012-08-24 Thread Friedrich W. H. Kossebau
Hi Andreas and Raphael, Am Freitag, 24. August 2012, 07:15:58 schrieb Andreas Pakulat: Hi, On Thu, Aug 23, 2012 at 11:58 PM, Friedrich W. H. Kossebau kosse...@kde.org wrote: I cannot reproduce this locally, but this might be just a timing issue. As this problem has not been reported

Re: internal lib name vs. output lib name, getting internal dependencies?

2012-08-24 Thread Andreas Pakulat
Hi, On Fri, Aug 24, 2012 at 10:22 AM, Friedrich W. H. Kossebau kosse...@kde.org wrote: Hi Andreas and Raphael, Am Freitag, 24. August 2012, 07:15:58 schrieb Andreas Pakulat: Yes, don't use the library name, use the target name, i.e. ${kastencore_LIB}. If the variable is not visible at the

internal lib name vs. output lib name, getting internal dependencies?

2012-08-23 Thread Friedrich W. H. Kossebau
Hi, I need your, the buildsystem experts', help. In the bugreport https://bugs.kde.org/show_bug.cgi?id=304794 the problem is reported that building of Okteta with parallel jobs fails, due to a library not created already when it is used to link to, cmp. this snippet from the attached log

Re: internal lib name vs. output lib name, getting internal dependencies?

2012-08-23 Thread Michael Pyne
On Thursday, August 23, 2012 23:58:22 Friedrich W. H. Kossebau wrote: When proposing solutions, please keep in mind that I try to keep the different modules as independent as possible, so moving things around/outside will not need big changes in the build system. First off, keep in mind that I

Re: internal lib name vs. output lib name, getting internal dependencies?

2012-08-23 Thread Friedrich W. H. Kossebau
Am Donnerstag, 23. August 2012, 18:05:32 schrieb Michael Pyne: On Thursday, August 23, 2012 23:58:22 Friedrich W. H. Kossebau wrote: When proposing solutions, please keep in mind that I try to keep the different modules as independent as possible, so moving things around/outside will not

Re: internal lib name vs. output lib name, getting internal dependencies?

2012-08-23 Thread Raphael Kubo da Costa
Friedrich W. H. Kossebau kosse...@kde.org writes: So the settings for the library libkasten2core is like this: libs/kasten/core/CMakeLists.txt has: --- 8 --- kde4_add_library( ${kastencore_LIB} SHARED ${kastencore_LIB_SRCS} ) set_target_properties( ${kastencore_LIB} PROPERTIES

Re: internal lib name vs. output lib name, getting internal dependencies?

2012-08-23 Thread Andreas Pakulat
Hi, On Thu, Aug 23, 2012 at 11:58 PM, Friedrich W. H. Kossebau kosse...@kde.org wrote: I cannot reproduce this locally, but this might be just a timing issue. As this problem has not been reported before, I am currently thinking this could be due to the recent change requested by the Windows