Hi everyone, I am attempting to compile AAF v1.2.0 on my M1 iMac (macOS 12.3 Monterey), using the MacOS ARM64 build instructions. I currently have Xcode 13.3 installed, as well as cmake 3.22.2 through homebrew.
When I get to this cmake command: % cmake -G "Xcode" -DPLATFORM=clang12 -DARCH=arm64 ../..
I do also have a homebrew version of clang through llvm, version 13.0.1, although the above output seems to show that cmake is using the built-in AppleClang 13.1.6. I attempted changing -DPLATFORM to clang13, and I also attempted running the x86-64 command instead, but both ended in the same error.
Any ideas? Thank you very much in advance.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have the same problem, and sadly don't have an answer.
However even though I get that error I do seem to be able to compile the library (so doing "cmake --build ." does seem to work.
So from the command line thats fine, most IDEs won't let me plough on and compile if the cmake generator failed sadly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After a bit of trial and error I found that if, in the tests/CMakeLists.txt file, you comment out the use of the axPlugin subdirectory:
#add_subdirectory(axPlugin)
the Xcode generator seems happy. No idea why it disliked that directory, maybe some bug later versions of Xcode have fixed but the file was exploiting.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
most IDEs won't let me plough on and compile if the cmake generator failed sadly
Do I understand this correctly that Xcode and other IDEs cannot load the generated project? I could not quickly figure out the cause of the CMake error and since command line build and tests worked decided to move on. If the error breaks IDE it's more severe than I thought.
comment out the use of the axPlugin subdirectory
This is helpful, thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ah maybe the xcode UI is a bit more lenient. I'm just using the xcode generator to build the equivalent of the makefiles, rather than using the xcode ui, and am using vscode to front-end it all.
So its perfectly possible that the gui version of xcode itself can ignore the error messages. FWIW I'm using vscode as we also do a lot of remote development, with the remote machines predominantly being Linux.
Sadly vscode concludes that the project can't be compiled if the 'generation' phase fails in any way. Which is probably a reasonable guess most of the time!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi everyone, I am attempting to compile AAF v1.2.0 on my M1 iMac (macOS 12.3 Monterey), using the MacOS ARM64 build instructions. I currently have Xcode 13.3 installed, as well as cmake 3.22.2 through homebrew.
When I get to this cmake command:
% cmake -G "Xcode" -DPLATFORM=clang12 -DARCH=arm64 ../..I get the following output ending with an error:
I do also have a homebrew version of clang through llvm, version 13.0.1, although the above output seems to show that cmake is using the built-in AppleClang 13.1.6. I attempted changing -DPLATFORM to clang13, and I also attempted running the x86-64 command instead, but both ended in the same error.
Any ideas? Thank you very much in advance.
Hi,
I have the same error.
I tried:
Any help would be much appreciated.
I have the same problem, and sadly don't have an answer.
However even though I get that error I do seem to be able to compile the library (so doing "cmake --build ." does seem to work.
So from the command line thats fine, most IDEs won't let me plough on and compile if the cmake generator failed sadly.
After a bit of trial and error I found that if, in the tests/CMakeLists.txt file, you comment out the use of the axPlugin subdirectory:
the Xcode generator seems happy. No idea why it disliked that directory, maybe some bug later versions of Xcode have fixed but the file was exploiting.
Hi Martin,
Do I understand this correctly that Xcode and other IDEs cannot load the generated project? I could not quickly figure out the cause of the CMake error and since command line build and tests worked decided to move on. If the error breaks IDE it's more severe than I thought.
This is helpful, thanks.
Ah maybe the xcode UI is a bit more lenient. I'm just using the xcode generator to build the equivalent of the makefiles, rather than using the xcode ui, and am using vscode to front-end it all.
So its perfectly possible that the gui version of xcode itself can ignore the error messages. FWIW I'm using vscode as we also do a lot of remote development, with the remote machines predominantly being Linux.
Sadly vscode concludes that the project can't be compiled if the 'generation' phase fails in any way. Which is probably a reasonable guess most of the time!