kdevplatform tries to link a static lib into a shared lib...

Alexander Neundorf neundorf at kde.org
Thu Aug 23 02:18:43 UTC 2007


On Wednesday 22 August 2007 02:40, Andreas Pakulat wrote:
> On 21.08.07 20:38:11, Alexander Neundorf wrote:
> > On Tuesday 21 August 2007 08:03, Andreas Pakulat wrote:
> > > On 21.08.07 07:53:57, Alexander Neundorf wrote:
> > > > On Tuesday 21 August 2007 06:03, Andreas Pakulat wrote:
> > > > > On 20.08.07 23:57:08, Alexander Neundorf wrote:
> > > > > > Please don't do this, this doesn't work on all platforms, sooner
> > > > > > or later there will be problems. Just use the source files
> > > > > > directly.
> > > > >
> > > > > No, the right solution is to make it a shared lib but there's
> > > > > nobody with the time for that at the moment. If you have a
> > > > > suggestion how to disable the plugin for all 64 bit I can quickly
> > > > > workaround the current build-problems on such systems (its not
> > > > > working on win32 anyway).
> > > >
> > > > Is the problem detecting the 64bit build ?
> > > > You could check CMAKE_SIZEOF_VOID_P ?
> > > > Of if some of the lib paths contain 64.
> > > > Maybe also CMAKE_SYSTEM_PROCESSOR, but that's not really reliable I
> > > > think.
> > >
> > > The problem is I have no idea how to check for 32 or 64 bit system
> > > during cmake-time, so I could do something like
> >
> > something like the following should do:
> > if(NOT CMAKE_SIZEOF_VOID_P EQUAL 8)
>
> That evaluates to true on 32 Bit systems right? (Just double-checking)

Yes (beside that I didn't test this line).

Bye
Alex




More information about the KDevelop-devel mailing list