[ 
https://issues.apache.org/jira/browse/PROTON-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948540#comment-14948540
 ] 

Otavio Rodolfo Piske commented on PROTON-1014:
----------------------------------------------

Yes I did:

➜  qpid-proton git:(master) ✗ ls build | wc -l 
0

➜  qpid-proton git:(master) ✗ cd build ; cmake 
-DCMAKE_INSTALL_PREFIX=/opt/devel/qpid-proton-0.11-SNAPSHOT 
-DSYSINSTALL_BINDINGS=ON .. && pwd && ( ls | wc -l) 
-- Build type is "Debug" (has debug symbols)
-- PN_VERSION: 0.11.0 (SNAPSHOT)
-- Emscripten (https://github.com/kripken/emscripten) is not installed: can't 
build JavaScript binding
-- Missing Ruby gem dependency: rspec
-- Missing Ruby gem dependency: simplecov
-- Skipping Ruby bindings due to missing dependencies...
-- Cannot find ruby, skipping ruby tests
-- Configuring done
-- Generating done
-- Build files have been written to: /home/opiske/code/cpp/rh/qpid-proton
/home/opiske/code/cpp/rh/qpid-proton/build
0



> Documentation: compilation instructions refer an invalid path
> -------------------------------------------------------------
>
>                 Key: PROTON-1014
>                 URL: https://issues.apache.org/jira/browse/PROTON-1014
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>            Reporter: Otavio Rodolfo Piske
>            Priority: Minor
>              Labels: documentation
>             Fix For: 0.11
>
>
> Documentation: compilation instructions refer an invalid path
> The compilation instructions, in file INSTALL.md, instructs the user to 
> create a build directory and switch to that directory for compilation. 
> However, no files are generated in the build directory and the 'make install' 
> step fails with the following error: 
> make: *** No rule to make target 'install'.  Stop.
> The users should be advised to: a) either configure and generate the 
> configuration in the project root directory or b) switch to the project root 
> after configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to