Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error in compiling #5

Closed
lmanchon opened this issue Mar 3, 2017 · 4 comments
Closed

error in compiling #5

lmanchon opened this issue Mar 3, 2017 · 4 comments

Comments

@lmanchon
Copy link

lmanchon commented Mar 3, 2017

--Hi

first command works fine: make build_3rdparty

[100%] Building CXX object src/toolkit/CMakeFiles/bamtools_cmd.dir/bamtools.cpp.o
Linking CXX executable ../../../bin/bamtools

but second failed:

make build_tools_release
rm -rf build-tools-Linux-Release;
mkdir -p build-tools-Linux-Release;
cd build-tools-Linux-Release;
qmake ../src/tools.pro "CONFIG-=debug" "CONFIG+=release" "DEFINES+=QT_NO_DEBUG_OUTPUT";
make;
qmake[1]: Entering directory /save/ngs-bits/build-tools-Linux-Release' qmake[1]: Nothing to be done for ../src/tools.pro'.
qmake[1]: Leaving directory /save/ngs-bits/build-tools-Linux-Release' make[1]: Entering directory /save/ngs-bits/build-tools-Linux-Release'
make[1]: *** No targets specified and no makefile found. Stop.
make[1]: Leaving directory `/save/ngs-bits/build-tools-Linux-Release'
make: *** [build_tools_release] Error 2

what's wrong ?

thank you --

@marc-sturm
Copy link
Member

marc-sturm commented Mar 3, 2017 via email

@lmanchon
Copy link
Author

lmanchon commented Mar 6, 2017 via email

@imgag
Copy link
Collaborator

imgag commented Mar 6, 2017

Hi Laurent,

looks like that is not Qt make, but standard GNU make.
It should look like that:

> qmake --version
QMake version 3.0
Using Qt version 5.2.1 in /usr/lib/x86_64-linux-gnu

What is the output of
> type qmake

In order to compile ngs-bits, you must install Qt5 and make sure that Qt qmake is in the path.

Best,
Marc

@imgag
Copy link
Collaborator

imgag commented Mar 13, 2017

I assume my last comment fixed the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants