Announcement

Collapse
No announcement yet.

Blank newly created android project fails to run.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Blank newly created android project fails to run.

    Hi,

    Created new project for Desktop, Android and iOS platforms. Wave 2.1.1.25 on Mac OS X 10.10.5 Yosemite.

    On building for Android emulator (Genymotion) received the following error:

    /Users/mfuser/Temp/TestPlatformsWave/packages/WaveEngine.2.1.1.25/build/MonoAndroid/WaveEngine.targets: Error: Command '"v2.0/Tools/VisualEditor/WaveConstantsCMD.exe" -i "/Users/mfuser/Temp/TestPlatformsWave/TestPlatformsWave.weproj" -o "/Users/mfuser/Temp/TestPlatformsWave/SharedSource/Main"' exited with code: 127. (TestPlatformsWave)
    Full build log:

    Building: TestPlatformsWaveSource (Debug)

    Building: TestPlatformsWave (Debug)

    Build started 4/16/2016 7:56:43 PM.
    __________________________________________________
    Project "/Users/mfuser/Temp/TestPlatformsWave/Launchers/Android/TestPlatformsWave.csproj" (Build target(s)):

    Target _CheckForContent:
    Properties/AndroidManifest.xml: warning XA0101: @(Content) build action is not supported

    Target BeforeBuild:
    ********** Constants process Begin **********
    Executing: "v2.0/Tools/VisualEditor/WaveConstantsCMD.exe" -i "/Users/mfuser/Temp/TestPlatformsWave/TestPlatformsWave.weproj" -o "/Users/mfuser/Temp/TestPlatformsWave/SharedSource/Main"
    /var/folders/4m/5vmcyk3n76vbxs7mpmzjbv040000gn/T/tmp3afe85a1.tmp: line 1: v2.0/Tools/VisualEditor/WaveConstantsCMD.exe: No such file or directory
    /Users/mfuser/Temp/TestPlatformsWave/packages/WaveEngine.2.1.1.25/build/MonoAndroid/WaveEngine.targets: error : Command '"v2.0/Tools/VisualEditor/WaveConstantsCMD.exe" -i "/Users/mfuser/Temp/TestPlatformsWave/TestPlatformsWave.weproj" -o "/Users/mfuser/Temp/TestPlatformsWave/SharedSource/Main"' exited with code: 127.
    Task "Exec" execution -- FAILED
    Done building target "BeforeBuild" in project "/Users/mfuser/Temp/TestPlatformsWave/Launchers/Android/TestPlatformsWave.csproj".-- FAILED

    Done building project "/Users/mfuser/Temp/TestPlatformsWave/Launchers/Android/TestPlatformsWave.csproj".-- FAILED

    Build FAILED.

    Warnings:

    /Users/mfuser/Temp/TestPlatformsWave/Launchers/Android/TestPlatformsWave.csproj (Build) ->
    /Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets (_CheckForContent target) ->

    Properties/AndroidManifest.xml: warning XA0101: @(Content) build action is not supported

    Errors:

    /Users/mfuser/Temp/TestPlatformsWave/Launchers/Android/TestPlatformsWave.csproj (Build) ->
    /Users/mfuser/Temp/TestPlatformsWave/packages/WaveEngine.2.1.1.25/build/MonoAndroid/WaveEngine.targets (BeforeBuild target) ->

    /Users/mfuser/Temp/TestPlatformsWave/packages/WaveEngine.2.1.1.25/build/MonoAndroid/WaveEngine.targets: error : Command '"v2.0/Tools/VisualEditor/WaveConstantsCMD.exe" -i "/Users/mfuser/Temp/TestPlatformsWave/TestPlatformsWave.weproj" -o "/Users/mfuser/Temp/TestPlatformsWave/SharedSource/Main"' exited with code: 127.

    1 Warning(s)
    1 Error(s)

    Time Elapsed 00:00:00.2086640

    ---------------------- Done ----------------------

    Build: 1 error, 1 warning
    Why plain vanilla project doesn't build?

    Thanks for help.

  • #2
    Up! Anybody?

    Comment


    • #3
      Hi mike,

      From MacOSX you can deploy on Mac or IOS but to deploy on Android WaveEngine only supports to deploy from Windows officially. But you can try to modify Android targets file following this instructions.

      1- Localize Android targets file inside of packages folder in your project:

      [YourProject]/packages/WaveEngine.2.1.1.25/build/MonoAndroid/WaveEngine.targets

      2- Edit WaveEngine.targets file

      Replace this line:
      Code:
      <Exec Command='"$(WaveEngine)v2.0\Tools\VisualEditor\WaveConstantsCMD.exe" -i "$(SolutionDir)$(ProjectName).weproj" -o "$(SolutionDir)SharedSource\Main"'/>
      With this:
      Code:
      <Exec Condition="'$(OS)' == 'Unix'" Command='mono "WaveConstantsCMD.exe" -i "$(SolutionDir)$(ProjectName).weproj" -o "$(SolutionDir)SharedSource/Main"' WorkingDirectory="/Library/Frameworks/WaveEngine.framework/v2.0/Tools/VisualEditor/"/> 
      Replace this line:
      Code:
      <Exec Command='"$(WaveEngine)v2.0\Tools\VisualEditor\WaveExporterCMD.exe" -m Project -t Android -p $(ProfileName) -i "$(SolutionDir)$(ProjectName).weproj" -o "$(SolutionDir)Intermediate\Content\$(ProfileName)"'/>
      With this
      Code:
      <Exec Condition="'$(OS)' == 'Unix'" Command='mono "WaveExporterCMD.exe" -m Project -t Android -p $(ProfileName) -i "$(SolutionDir)$(ProjectName).weproj" -o "$(SolutionDir)Intermediate/Content/$(ProfileName)"' WorkingDirectory="/Library/Frameworks/WaveEngine.framework/v2.0/Tools/VisualEditor/"/>
      Replace this line:
      Code:
      <Exec Command='xcopy /E /I /Y "$(SolutionDir)Intermediate\Content\$(ProfileName)\*.*" "$(TargetDir)\Content\"'/>
      With this:
      Code:
      <Exec Condition="'$(OS)' == 'Unix'" Command='rsync -aruv "$(SolutionDir)Intermediate/Content/$(ProfileName)/" "$(TargetDir)Content/"'/> 

      I hope that you find it useful

      We will add this lines to next Android targets release.

      Thanks for your feedback!
      Jorge Canton

      Comment


      • #4
        Thanks, I'll try to follow the recipe and will report back the results.

        UPD: It works !!

        In second command: -m Project -t iOS

        Should it be instead: -m Project -t Android

        ?
        Last edited by mike.g; 04-21-2016, 07:59 AM.

        Comment


        • #5
          Excellent mike.g!

          Please keep us posted on your progress!!

          Comment


          • #6
            Hi mgomar !

            My current status with Wave Engine is here: http://forum.waveengine.net/forum/ge...-in-the-editor

            I really like how Wave Engine is written but the editor and tooling... frankly, I think I'll switch to another, more production ready 2d game engine...

            Comment


            • #7
              Ok, thanks!
              We will continue on the other thread.

              Comment

              Working...
              X