I am trying to automatically generate some mutation for a java program using Major through Mac terminal. And in Major's document, it states installation is just to unzip the folder. However, my terminal seems not to recognize the Major commends, in other words, it is not using the Major compiler. Has anyone encountered a similar situation? What should I do to use its compiler?
http://mutation-testing.org/doc/major.pdf
Solved
Solution by adding it to the executable path in terminal:
export PATH="/Users/username/Desktop/major-1.1.7_jre7/major/bin:$PATH"
Related
I'm trying to run the Kotlin/Native Hello Program
but the terminal says the command kotlin-native cannot be found. I'm on a MacBook, using zsh (get same error when I use bash) and installed Kotlin via Homebrew before, so kotlin and it's compiler works on my machine, the kotlinc command works just fine. I'm trying to use the compiler instead of gradle for now. Is there a different command I'm supposed to be using?
It sound like you may have had a similar problem to me. Installing kotlin-native via homebrew did not install the kotlinc-native command.
To get the command working, I had to do the following:
Go to https://github.com/JetBrains/kotlin/releases and get the latest version of Kotlin
Extract it to .kotlin in the home directory
Add export PATH="$HOME/.kotlin/bin:$PATH" to .zshrc
The problem with this method is that it's completely disconnected from Homebrew. You will have to run the steps again every time you want to update Kotlin.
You've typed kotlin-native but the tutorial says kotlinc-native, which is the actual name of the process file.
If kotlinc works then you might just have a typeo.
I don't use these processes directly, but I'm somewhat familiar with them. My guess is check the name.
I have the following problem:
I am on Ubuntu 20.04 and I am trying to set up GNUstep which is required for certain source binaries I want to build
(for the sake of completion, the program I want to build is called Advanced Rendering Toollḱit, information can be found here: https://cgg.mff.cuni.cz/ART/).
When building with the clang-9 compiler, after invoking the make command, I receive this error message:
fatal error: 'objc/objc.h' file not found
I should mention that I am still fairly new to Linux in general. What I did was installing GNUstep via
sudo apt-get install gnustep gnustep-devel
as advised on the website (http://wiki.gnustep.org/index.php/GNUstep_under_Ubuntu_Linux). It resulted in receiving the mentioned error.
/usr/include/GNUstep/Foundation/Foundation.h:31:9: fatal error: 'objc/objc.h' file not found
The next thing I tried was to download the provided configuration scripts from the same webpage and execute them. When I did, I received the following feedback:
checking whether objc really works... no. I don't seem to be able to use your Objective-C compiler to produce
working binaries! Please check your Objective-C compiler installation.
If you are using gcc-3.x make sure that your compiler's libgcc_s and libobjc
can be found by the dynamic linker - usually that requires you to play
with LD_LIBRARY_PATH or /etc/ld.so.conf.
Please refer to your compiler installation instructions for more help.
configure: error: The Objective-C compiler does not work or is not installed properly.
Maybe I am getting something wrong, however, my whole intention of installing GNUstep is to make Objective-C programming possible on a non-Apple machine. Therefore I do not understand why it is complaining about a non-working Objective-C compiler (by the way, I end up with the same result when using gcc and g++ as compilers).
I did do some research and I came across some StackOverflow posts, suggesting me to install libobjc2, but I suspect this to be depreciated with Ubuntu 20.04.
I honestly don't know what's wrong and I highly appreciate a little push in the right direction! Many thanks in advance for helping me!
Although I cannot tell what exactly the bug was in my case, I got some external help and together we came up with a solution that worked for me.
For debugging purposes, we created a test user account in my Ubuntu environment and repeated the whole process. It worked flawlessly.
We concluded that something must have been wrong locally with regard to my user account. I am sure there was something wrong with my environment variables, although I failed to clearly identify the bug (I am a Linux beginner). I chose the easy way out, backed up important files, deleted and re-created my root user account and then it worked. I hope, this may help any other who has the same problem.
#skaak, thank you for your help and suggestions!
As people are pointing, if you want to use clang to compile objective C programs in Ubuntu you have to install libobjc2 (mainstream project here) but it's currently not packaged in Ubuntu. It's possible that there was a package with the same or similar name, as you found out, but that was a different thing. This manual installation worked for me:
wget https://github.com/gnustep/libobjc2/archive/v2.0.tar.gz
tar xvzf v2.0.tar.gz
cd libobjc2-2.0
mkdir build
cd build
export CC=`which clang`
export CXX=`which clang++`
cmake ..
make
sudo make install
Trying to set up IntelliJ IDEA with the Lua plugin. This requires me to direct it to the location of a Lua SDK. All instructions I have been able to find for this are on a Windows system, pointing to a specific directory in Program Files. I am running a Linux system. I've built and installed Lua 5.3.4 (newest version at time of writing) from source, but as far as I can tell that doesn't include any equivalent to the SDK needed – it just drops a variety of necessary files in /usr/local/{bin,include,lib,man/man1} and creates two empty directories /usr/local/{lib,share}/lua/5.3.
Am I missing something conceptual? Do I need to get something else (the existence of which I have been unable to confirm)? Should I just give up on this and find another IDE? The plugin seems to come with two SDKs, Kahlua and LuaJ, but I don't know how well either of these match up to either standard Lua or LuaJit, which are what I would be using.
This is assuming you are using this Lua plugin for IntelliJ:
If you have installed Lua via DNF or yum simply guide IntelliJ to /urs/bin and it'll find it. (I assume this also works for other installers like apt or brew.)
It looks like the SDK is just looking for two files lua and luac which both live in /usr/bin.
I want to use KDL (Kinematics and Dynamics Library) in robot control box. But robot control box uses SCons as their build system while KDL uses CMake.
It turned out that the control box doesn't have CMake installed. Should I install CMake in the control box? Or write SCons file for compiling KDL?
====================================================
My question is ambiguous. Sorry for that. And unfortunately, I cannot show the link of Control Box, it's not public. Here is link of KDL installation manual.
http://www.orocos.org/kdl/installation-manual
Let me make it more clear.
Forget all of previous question above and all about Control box, KDL. Let's say that you want to use one library. But the library can be built using CMake according to installation manual. Your PC doesn't have CMake installed but it has SCons, and unfortunately you should not install CMake on your PC.
If you can only use SCons, what can you do?
I know this situation is not usual, I want to know your opinion.
To answer your initial question: Yes, you should always try to install CMake, if that is a build requirement for you library and if you need to build that library from the sources.
To answer your later question: Replacing or rewriting the build system scripts is a major effort and not advisable. In general there is no script to convert build-systems. Such script might help to make the manual transformation. If you have a look at LLVM's effort to replace Autotools by CMake or Boost replacing it's own build system by CMake, you find out it takes several people several years and still not everybody is satisfied.
Often you don't need to build the library yourself. Either there are already built packages from the project directly of from your distribution (Debian etc. packages) or third party packagers like Mac Ports or NuGet.
In your case KDL provides Debian/Ubuntu packages.
Additional KDL is part of ROS, which is experimental in Homebrew for OS X.
Im having a very annoying issue with qtcreator and cmake projects: qtcreator fails to find the executable. It just prints "No executable specified" when trying to launch any executable from the IDE. Everything works fine after configuring the project (first time only). The issue manifests when loading the project afterwards. Only workaround is deleting the "CMakeLists.txt.user" before every use. This is tedious and unnecessary.
This is happening to projects that were running just fine for years, both my own and my colleagues, on multiple machines running ubuntu 14.04 & 14.10. Problems started with qtcreator version 3 and higher from ubuntu 14.04 upwards.
Assuming that the issue is triggered by some changes in the "CMakeLists.txt.user", after the project is closed the first time, I replaced the file with a copy of it right after it was created the first time. This worked, thus confirming that there is either something wrong with the file itself, or changes to it trigger an existing bug in qt-creator. Unfortunately it is just as tedious as deleting the file in the first place.
My Challenge:
Unfortunately I am not familiar with the inner workings of qtcreaor, however I managed to identify the specific config lines that are responsible. What does qtcreator actually change here?
Please note that "racoon" is the project name and the above diff screenshot is much larger than formatted by stackoverflow (right-click to view full resolution).
Thank you.
i had exactly the same problem using Ubuntu 14.10 and resolved it by doing the following:
Get ftp://ftp.pbone.net/mirror/ftp.sourceforge.net/pub/sourceforge/a/an/anthonos/mirror/os3-next/os3-rpm/q/qtcreator-3.1.2-0.x86_64.rpm
Extract the file /usr/lib/qtcreator/plugins/QtProject/libCMakeProjectManager.so
Overwrite this file at
/usr/lib/x86_64-linux-gnu/qtcreator/plugins/ ( at least on x64)
in your system
This will replace the cmake plugin which is currently version 3.1.1 with 3.1.2 which will make the problem disappear !
I installed qtcreator using Qt's own installer instead of the one provided by Ubuntu. It installs version 5.3.1 and fixes the problem.