On 28.05.2014 05:28, J Decker wrote:
patching latest source, bypassing my location test code and added
set( CMAKE_PLATFORM_NO_SONAME_SUPPORT ON )
then the patch seems to generate 'correct' commandlines... and the
result works.
Thank you for testing.
I proposed a modified version (restrict
patching latest source, bypassing my location test code and added
set( CMAKE_PLATFORM_NO_SONAME_SUPPORT ON )
then the patch seems to generate 'correct' commandlines... and the result
works.
On Tue, May 27, 2014 at 4:18 AM, J Decker wrote:
>
>
>
> On Tue, May 27, 2014 at 3:30 AM, Nils Gladitz
On Tue, May 27, 2014 at 3:30 AM, Nils Gladitz wrote:
> On 05/27/2014 12:25 PM, J Decker wrote:
>
>> Without modification
>> target_link_libraries( ${target} ${target_lib} )
>>
>> generates a link command like this
>>
>
> Yeah I think I got that part ... which is why I proposed modification.
>
On 05/27/2014 12:25 PM, J Decker wrote:
Without modification
target_link_libraries( ${target} ${target_lib} )
generates a link command like this
Yeah I think I got that part ... which is why I proposed modification.
Or do you mean that is the result after applying the patch?
Nils
--
Pow
Without modification
target_link_libraries( ${target} ${target_lib} )
generates a link command like this
gcc.exe --sysroot=c:/.../platforms/android-14/arch-arm -fPIC -g -D_DEBUG
-lstdc++ -lgnustl_static -shared -o
libEditOptions.code.soCMakeFiles/EditOptions.code.dir/editopt.c.obj
-Lc:\.
On 05/27/2014 11:10 AM, J Decker wrote:
These result from the libraries resulting from the built sources, not
from the sysroot libs or things discovered with find packages.
I probably don't fully understand the issue but couldn't this easily
enough be patched in CMake itself (e.g. attached un
These result from the libraries resulting from the built sources, not from
the sysroot libs or things discovered with find packages.
On Tue, May 27, 2014 at 1:37 AM, Hendrik Sattler wrote:
> Can this be solved with CMAKE_STAGING_PREFIX or CMAKE_SYSROOT in CMake 3.0?
> From the documentation, it
Can this be solved with CMAKE_STAGING_PREFIX or CMAKE_SYSROOT in CMake 3.0?
>From the documentation, it looks like to have exactly this purpose.
On 26. Mai 2014 23:06:51 MESZ, J Decker wrote:
>if it exists as a target; I need to know the path to the built library
>for
>subsequent projects to link
if it exists as a target; I need to know the path to the built library for
subsequent projects to link against. I have to manually add the option
-Lwrote:
> Maybe you can explain _why_ you need to do it this way? Can it be solved
> more inline with the better cross-compile support in cmake-3.0?
>
Maybe you can explain _why_ you need to do it this way? Can it be solved more
inline with the better cross-compile support in cmake-3.0?
On 26. Mai 2014 19:29:20 MESZ, J Decker wrote:
>So... no alternatives to location in this instance?
>
>
>On Sat, May 24, 2014 at 7:28 PM, J Decker wrote:
>
>>
So... no alternatives to location in this instance?
On Sat, May 24, 2014 at 7:28 PM, J Decker wrote:
> CMake Warning (dev) at
> C:/general/build/android/karaway/debug_out/core/DefaultInstall.cmake:203
> (get_property):
> Policy CMP0026 is not set: Disallow use of the LOCATION target property.
CMake Warning (dev) at
C:/general/build/android/karaway/debug_out/core/DefaultInstall.cmake:203
(get_property):
Policy CMP0026 is not set: Disallow use of the LOCATION target property.
Run "cmake --help-policy CMP0026" for policy details. Use the
cmake_policy
command to set the policy and su
12 matches
Mail list logo
