Skip to content
This repository has been archived by the owner on Sep 1, 2023. It is now read-only.

CMake files generated in $NUPIC not $NUPIC/build #770

Closed
breznak opened this issue Apr 4, 2014 · 6 comments
Closed

CMake files generated in $NUPIC not $NUPIC/build #770

breznak opened this issue Apr 4, 2014 · 6 comments

Comments

@breznak
Copy link
Member

breznak commented Apr 4, 2014

since recent update cmake files ignore the current directory from which cmake is called and are created in $NUPIC

cd $NUPIC/build
cmake ..

files created in $NUPIC

I noted some changes in variable names for project output dir, maybe related?

@breznak breznak added this to the Sprint 19 milestone Apr 4, 2014
@breznak breznak added the bug label Apr 4, 2014
@breznak
Copy link
Member Author

breznak commented Apr 4, 2014

CC @david-ragazzi

@david-ragazzi
Copy link
Contributor

I noted some changes in variable names for project output dir, maybe related?

Certainly! I prefer "standardize" these names. Please see this (my first comment): numenta/nupic.core-legacy#47

quote:

They are generated by default on
nupic.core/build/release folder, however any user could change its
destination using cmake -DPROJECT_BUILD_RELEASE_DIR=… or cmake -DPROJECT_BUILD_TEMP_DIR=… command line.

@breznak
Copy link
Member Author

breznak commented Apr 4, 2014

I mean the Cmake file changed it's behavior:

cmake $NUPIC Build files have been written to: /home/nupic/nupic-source nupic@nupic-vm:~/nupic-source/build/release$ ls nupic@nupic-vm:~/nupic-source/build/release$ pwd /home/nupic/nupic-source/build/release
it ignores that I;m in build/release

@breznak
Copy link
Member Author

breznak commented Apr 4, 2014

CMakeLists has
Build dir: ${PROJECT_BIN_DIR}
(which evaluates to $NUPIC) and is never used in the cmakefile.

@breznak
Copy link
Member Author

breznak commented Apr 4, 2014

to clarify, I'm talking about the config files cmake generates (eg Makefile), not the resulting files from compilation.

@david-ragazzi
Copy link
Contributor

This was discussed ans solved at #751 . Closing...

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

No branches or pull requests

3 participants