Re: [wxlua-users] stedit lib location

[John L. <jla...@gm...>]

On Fri, Jun 15, 2012 at 3:31 PM, klaas.holwerda <ng...@kl...> wrote:
> On 15-6-2012 6:08, John Labenski wrote:
>> I not sure if what these files contain is useful or not. They're what cmake generates, but they'll
>> be wrong once installed or if moved.
> Did not know that CMake generated them. I thought you made them. What exactly triggers that??

export( TARGETS LuaLib wxLuaLib wxLuaDebugLib wxLuaSocketLib wxLuaBindLib
        FILE "${CMAKE_BINARY_DIR}/build/wxLua-config.cmake")

They are now also installed using INSTALL( TARGETS target1 EXPORT...)
then INSTALL(EXPORT ...)

>>> INCLUDE_DIRECTORIES(  "${ BUILD_INSTALL_PREFIX }/include" )
>> I don't understand, what automatically adds this? I don't think I have
>> any include paths using the BUILD_INSTALL_PREFIX.
> That is what i say. And that it might be a good idea o add it standard when using a central install
> directory.
> Like if wxstedit uses  BUILD_INSTALL_PREFIX location the same as wxLua and wxWidgets wxArt2d etc.,
> it is clear that wxLua
> will need to look there also for the installed wxstedit headers.

There will be a problem if you install wxLua/wxStEdit then get a new
version and need to rebuild it. The compiler include search paths can
be ordered to look locally first, but I feel like it would be
confusing to automatically add the search path to the old version.  I
think it is best to make the user point to the extra include paths.

Actually, I plan to use SVN externals to do a checkout of wxStEdit
into the wxLua tree and that way the two can be built together very
easily.

Try the make install now... it should be much better.

Regards,
     John