I downloaded an openflow for OMNeT 5.5.1 and inet 3.6.6 from the following link:
https://github.com/CoRE-RG/OpenFlow
When I build the project it could not create libopenflow_dbg.dll file, and it gives the following errors:
make[1]: *** [Makefile:164: ../out/clang-release/src/libopenflow.dll] Error 1
The log shows that you try to build project in release mode. Therefore change the mode to debug (i.e. right-click on project and select Build Configuraions | Set Active | debug). Do the same for INET.
If errors will continue to occur set verbose output by opening Properties of the project | C/C++ Build | Behavior and in the Build field add V=1 at the end. Then build project, and go to the first error in the log, and insert this error in your question.
Related
Every time I'm starting a debug in IntelliJ I receive:
Error occurred during initialization of VM
agent library failed to init: instrument
Failed to find Premain-Class manifest attribute in /Users/me/.m2/repository/org/jetbrains/kotlinx/kotlinx-coroutines-core/1.4.3/kotlinx-coroutines-core-1.4.3.jar
Process finished with exit code 1
I already
Restarted, invalidated caches
Updates all dependencies in the POM
Re-downloaded the project
Reset the project to various old branches
Deleted local maven cache
It only occurs when I want to debug. Test, compile, run, all works - just debug doesn't. Debug works as usual on all other projects.
Has anyone an idea what the hell is going on?
There was an issue: KTIJ-17927 Debugger: "Failed to find Premain-Class manifest attribute" when debugging main function in jvmMain in MPP with coroutines
The workaround is to set File | Settings | Build, Execution, Deployment | Debugger | Data Views | Kotlin | Disable coroutine agent option. Or update to the latest IDE and Kotlin plugin version where it should be fixed.
I have a project that needs to be uploaded to my private pods. Because it depends others and there is an error: Multiple commands produce. I have set my xcode like that：File - worksapce - build system - Legacy Build System.It can run on top of my xcode success.
But when I execute the command: pod repo push XXX XXX. Podspec - sources = 'xxx, https://github.com/CocoaPods/Specs' --verbose --allow-warnings --use-libraries. The mistake was repeated:
Build system information
error: Multiple commands produce '/Users/joker/Library/Developer/Xcode/DerivedData/App-fdhxxtrwyvhdkcapwibarbetxoyu/Build/Products/Release-iphonesimulator/App.app/Info.plist':
1) That command depends on command in Target 'App' (project 'App'): script phase “[CP] Copy Pods Resources”
2) Target 'App' (project 'App') has process command with output '/Users/joker/Library/Developer/Xcode/DerivedData/App-fdhxxtrwyvhdkcapwibarbetxoyu/Build/Products/Release-iphonesimulator/App.app/Info.plist'
** BUILD FAILED **
Testing with `xcodebuild`.
-> XXX (89)
- WARN | url: The URL (https://gitee.com/Becent/BCStarRocket) is not reachable.
- ERROR | [iOS] xcodebuild: Returned an unsuccessful exit code.
- NOTE | xcodebuild: note: Using new build system
- NOTE | [iOS] xcodebuild: note: Planning build
- NOTE | [iOS] xcodebuild: note: Constructing build description
Testing with xcodebuild, xcodebuild: note is Using new build system, not Legacy Build System.
The issue might be occurring because of multiple Plist or other files within App-
Solution -> Open target -> Build phases > Copy Bundle Resources and remove info.plist from there.
Xcode 10 Error: Multiple commands produce
I am unable to generate the code coverage data when the the workspace is built with custom XCODE_CONFIGURATION_BUILD_DIR.
We run the xcodebuild commands to build the workspace with a XCODE_CONFIGURATION_BUILD_DIR, so that multiple jenkins CI jobs won't overwrite the build output of other jobs which are also running concurrently.
When we run the tests for a build generated this way and try to get the code coverage report, the command fails with the below error.
jenkins$ xcrun xccov view *.xccovreport
Errors:
Error Domain=IDEFoundationErrorDomain Code=14 "Failed to merge raw profiles in directory /Users/jenkins/Library/Developer/Xcode/DerivedData/XXXXXX-buggtqumttnpjvejnbfhulhqcvno/Build/ProfileData/bff950eda0f75b2dbadb3ce08510474b4667ac82 to destination /Users/jenkins/Library/Developer/Xcode/DerivedData/XXXXXX-buggtqumttnpjvejnbfhulhqcvno/Build/ProfileData/bff950eda0f75b2dbadb3ce08510474b4667ac82/Coverage.profdata: No profile data files were written to '/Users/jenkins/Library/Developer/Xcode/DerivedData/XXXXXX-buggtqumttnpjvejnbfhulhqcvno/Build/ProfileData/bff950eda0f75b2dbadb3ce08510474b4667ac82'" UserInfo={NSLocalizedDescription=Failed to merge raw profiles in directory /Users/jenkins/Library/Developer/Xcode/DerivedData/XXXXXX-buggtqumttnpjvejnbfhulhqcvno/Build/ProfileData/bff950eda0f75b2dbadb3ce08510474b4667ac82 to destination /Users/jenkins/Library/Developer/Xcode/DerivedData/XXXXXX-buggtqumttnpjvejnbfhulhqcvno/Build/ProfileData/bff950eda0f75b2dbadb3ce08510474b4667ac82/Coverage.profdata: No profile data files were written to '/Users/jenkins/Library/Developer/Xcode/DerivedData/XXXXXX-buggtqumttnpjvejnbfhulhqcvno/Build/ProfileData/bff950eda0f75b2dbadb3ce08510474b4667ac82'}
Version/Build:
Version 10.1 (10B61)
Found this thread on Github
The issue was: generating coverage for a Static Library fails, but not for a Dynamic Library.
So check if it works, changing on pbxproj:
- MACH_O_TYPE = staticlib;
+ MACH_O_TYPE = mh_dylib;
And it really generated coverage successfully on my sample framework.
The solution which worked for me was, I have changed the Mach-O-Type from Executable to Static Library.
With the option Dynamic Library also, the coverage report was generating but the build was failing.
Another option was to set the test target as Static Library and Main Target as Executable. Build Succeeded and able to see the coverage for multiple targets.
Xcode Version : 13.4
When I build in Terminal, I can use a flag to say I want to build for GUI:
go build -ldflags="-H windowsgui"
However, I just started using JetBrains Goland and I don't how to run GUI apps. What can I do?
go build will only build the application.
To actually run the application, you should go to Run | Edit Configurations... | + | Go Application and configure the application as you need.
Here you will need to set two options:
add -ldflags="-H windowsgui" to the Go tool arguments option
configure the Output directory to be in the same directory as your .manifest file
Setting the output directory is critical in order to run the the application without encountering the following panic panic: TTM_ADDTOOL failed described in this issue.
Then you can run the configuration via Run | Run... and select the configuration you've just created.
We have our own GCC based compiler. We use eclipse in order to develop .c files using our compiler – after hitting the build button eclipse manages to run our ‘make’ file and the build operation succeeds.
We’re trying to configure the eclipse project such that it will use this compiler in order to show the compilation errors as red underline marks during the code-writing stage.
In order to do so, we add the following configurations:
Project properties > C/C++ Build>Tool chain editor > current toolchain: “Cross GCC”, current builder: “CDT internal builder”
Project properties > C/C++ Build>Settings>Tool Settings>Cross Settings> - here I set the prefix and the path of my GCC compiler.
Project properties > C/C++ General > Preprocessor include path, Macro etc. > providers > check: “CDT Cross Build Output Parser” and inside check “Allocate console in the console view”.
After doing that we get the following error in the console view:
i486-elf-g++ -E -P -v -dD
C:/Users/workspace/.metadata/.plugins/org.eclipse.cdt.managedbuilder.core/spec.C
Cannot run program "i486-elf-g++": Launching failed Error: Program
"i486-elf-g++" not found in PATH
It looks like eclipse is trying to compile a file named “spec.C”, in the plugin directory. We tried to look for that file and we only found an auto-generated file called “spec.c” (lower case .c) that is empty.
Our compiler executable name is “i486-elf-gcc”.
What additional steps need to be done?
Note that running the make file using the “build” button completes without errors or warnings.
Thanks
This is not related to the spec.c. It seems that the path of the i486-elf-gcc is not in the PATH variable. You can add the path the PATH-varaible in the "Environment" -tab