AndroidTacticalAssaultKit-CIV icon indicating copy to clipboard operation
AndroidTacticalAssaultKit-CIV copied to clipboard

Conan install failed='1'

Open sunsongwen123 opened this issue 2 years ago • 5 comments

Hello, I am following the same example and also tried original and I am getting following error. Searched all over but no luck. Any help will be much appreciated.

` Execution failed for task ':libtakengine:generateJsonModelCivDebug'.

/home/ashok/StudioProjects/AndroidTacticalAssaultKit-CIV/takengine/takengine/CMakeLists.txt : C/C++ civDebug|armeabi-v7a : CMake Error at /home/ashok/StudioProjects/AndroidTacticalAssaultKit-CIV/takengine/takengine/cmake/support/conan.cmake:631 (message): Conan install failed='1' Call Stack (most recent call first): CMakeLists.txt:108 (conan_cmake_install) `

Originally posted by @prajapak in https://github.com/deptofdefense/AndroidTacticalAssaultKit-CIV/issues/6#issuecomment-1067454158

sunsongwen123 avatar Aug 12 '22 09:08 sunsongwen123

I have run into this error message as well. Were you able to resolve this?

I noticed some conan.py and "missing cmakelists.txt" errors when I execute my prebuild.sh and am wondering if it is related but have no way to tell. I believe I have followed the documentation but I cannot get the project to build.

Alayan2 avatar Sep 07 '22 13:09 Alayan2

I've been getting the same error and haven't been able to fix it yet. I've notice error outputs are dependent on the JDK path. Changing the java pathing in android studio: settings-> build,execution,deployment-> gradle. ive gotten it to exhibit two other similar errors.

Error 1: Execution failed for task ':takkernel:engine:generateJsonModelDebug'.

> /home/jeremyruroede/AndroidTacticalAssaultKit-CIV/takkernel/engine/CMakeLists.txt : C/C++ debug|arm64-v8a : CMake Error at /home/jeremyruroede/AndroidTacticalAssaultKit-CIV/takkernel/engine/cmake/support/ValidateJavaExists.cmake:55 (message):
    32-bit Java specified while targeting a 64-bit build.
  Call Stack (most recent call first):
    src/main/jni/CMakeLists.txt:7 (validate_java_exists)

Error 2:

Task :takkernel:engine:generateJsonModelDebug FAILED

/home/jeremyruroede/AndroidTacticalAssaultKit-CIV/takkernel/engine/CMakeLists.txt : C/C++ debug|armeabi-v7a : CMake Warning at /home/jeremyruroede/AndroidTacticalAssaultKit-CIV/takkernel/engine/CMakeLists.txt:108 (find_package):
  By not providing "Findkhronos.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "khronos", but
  CMake did not find one.

  Could not find a package configuration file provided by "khronos" with any
  of the following names:

    khronosConfig.cmake
    khronos-config.cmake

  Add the installation prefix of "khronos" to CMAKE_PREFIX_PATH or set
  "khronos_DIR" to a directory containing one of the above files.  If
  "khronos" provides a separate development package or SDK, be sure it has
  been installed.

To which i verified jdk path and 64bit version.

Has anyone had any luck with this? ive reached out to the ATAK discord and will report back with a fix if i get one working.

Dawgomatic avatar Dec 29 '22 19:12 Dawgomatic

Try setting Gradle JDK pathing in android studio: file-> settings-> build,execution,deployment-> Build Tools -> gradle to 1.8[version 1.8.0_352 /usr/lib/jvm/java-8-openjdk-amd64 ]

if you can get it to exhibit the error:

> /home/jeremyruroede/AndroidTacticalAssaultKit-CIV/takkernel/engine/CMakeLists.txt : C/C++ debug|arm64-v8a : CMake Error at /home/jeremyruroede/AndroidTacticalAssaultKit-CIV/takkernel/engine/cmake/support/ValidateJavaExists.cmake:55 (message):
    32-bit Java specified while targeting a 64-bit build.
  Call Stack (most recent call first):
    src/main/jni/CMakeLists.txt:7 (validate_java_exists)

see issue - https://github.com/deptofdefense/AndroidTacticalAssaultKit-CIV/issues/236

I describe the fix there.

Dawgomatic avatar Jan 01 '23 00:01 Dawgomatic

same problem, did you solve this?

zybao avatar Sep 18 '23 06:09 zybao

@zybao The ATAK Discord channel can help you. I think there are pinned documents in that channel outlining how to make this work.

Something to note: it wasn't clear to me when I posted here that you do not have to follow this installation guidance to start developing an ATAK plugin. There is a plugintemplate that you can start building on and a developer version of ATAK in the release zip file. For my purposes, this was enough to start ATAK development. If you actually need to contribute to this ATAK repo, then reach out to the ATAK Discord channel for prompt assistance: https://discord.gg/buMv9RCH

Alayan2 avatar Sep 18 '23 14:09 Alayan2