[jira] [Commented] (PROTON-1014) Documentation: compilation instructions refer an invalid path
[ https://issues.apache.org/jira/browse/PROTON-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950039#comment-14950039 ] Otavio Rodolfo Piske commented on PROTON-1014: -- Well, git clean -fd didn't do the trick, but cloning the project again and running the install steps as documented in INSTALL.md did the trick. As you said, I have, probably, run a in-tree cmake. Thanks! > 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 >Assignee: Bozo Dragojevic >Priority: Minor > Labels: documentation > > 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)
[jira] [Commented] (PROTON-1014) Documentation: compilation instructions refer an invalid path
[ https://issues.apache.org/jira/browse/PROTON-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948499#comment-14948499 ] Robbie Gemmell commented on PROTON-1014: Did you use cmake before running make? The cmake step described is what populates the build dir after you switch to it. > 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)
[jira] [Commented] (PROTON-1014) Documentation: compilation instructions refer an invalid path
[ https://issues.apache.org/jira/browse/PROTON-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948636#comment-14948636 ] Robbie Gemmell commented on PROTON-1014: Hmm, not sure then I'm afraid. If I run commands like you gave above, the build dir does get populated as expected. The documentation seems to be correct to me, and describes the general process I'd expect and behaviour I have always seen. One difference is I get a lot more output from cmake than your snippet above contains. I do get a similar/reduced amount out output if i re-run cmake in the build dir after it is already been populated. Presumably you are getting this reduced output because it is actually working in the parent dir for some reason, as noted in your output about where it has written the files. Perhaps someone more familiar with cmake and the C build in general can chime in. > 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)
[jira] [Commented] (PROTON-1014) Documentation: compilation instructions refer an invalid path
[
https://issues.apache.org/jira/browse/PROTON-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948907#comment-14948907
]
Bozo Dragojevic commented on PROTON-1014:
-
bq. – Build files have been written to: /home/opiske/code/cpp/rh/qpid-proton
why is there /build missing at the end of this line in your output..
here is how it looks for me:
{code}
vagrant@builder:/vagrant/qpid-proton$ mkdir PROTON-1014 && cd PROTON-1014 &&
cmake ..
-- The C compiler identification is GNU 4.8.4
-- Check for working C compiler: /usr/bin/cc
[[[ lots of stuff removed ]]]
-- Configuring done
-- Generating done
-- Build files have been written to: /vagrant/qpid-proton/PROTON-1014
{code}
> 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)
