Skip to content
This repository has been archived by the owner on May 16, 2020. It is now read-only.

Some confuses #7

Open
Doutianbao opened this issue Feb 10, 2017 · 1 comment
Open

Some confuses #7

Doutianbao opened this issue Feb 10, 2017 · 1 comment
Labels

Comments

@Doutianbao
Copy link

Running in Debian 8.7
According to the document, succeed in compiling the deps.
But when it comes to the Dev-compile process,

 1.terminater shows:
        docxu@debian:~/Dev/Install/Debug$ ninja 
         [19/22] Automatic MOC for target ioPacs
# I am confusee that why it's not [22/22]   

2. Not the same as compiling the deps, the document  says:cmake  in Dev/Build/Debug, But nothing was built in Dev/Build/Debug, like everything goes to Dev/Install/Debug. So, I ninjia in  Dev/Install/Debug.
# Is there anything wrong?

3.Can you upload some videos about Tuto ,usage or something like research progress?

I am soooooooooooooooooooooooooo sorry about my poor English. Still hope fw4spl turn out in debain-med.

Thank you all for the big work:)

@schweitzer
Copy link
Member

Thanks for using fw4spl.

I will try to answer your questions.

  1. Yes you're right it should be [22/22], have you set a project name in the cmake option PROJECT_TO_BUILD ?

  2. Compiling the Deps and compiling fw4spl are two different processes:

  • In the Deps the build command (make or jom) do first the build and automaticaly the install process, that's why everything goes in dev/deps/install/debug

  • In fw4spl the build process is more close to the cmake standard.
    For example:

    • fw4spl sources in dev/src/fw4spl
    • fw4spl build in dev/build/debug
    • fw4spl install in dev/install/debug

I think that running ninja in install folder is not a good idea.

See the documentation for further information about our build process.

  1. No videos are planned for now... sorry 😉

fbridault pushed a commit that referenced this issue Mar 9, 2017
Added new ::fwData::Landmarks (see #4)
Replaced the adaptor ImageLandmark by SLandmarks (see #6)
Added new editor for landmarks (see #5)
Updated the configuration to use the new landmarks in VRRender (see #7)


See merge request !32
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants