0.7.700 Alpha Ready For Testing

[varlog]

Originally Posted by DiapDealer

Do you mean that you've set your install prefix to the same directory as the build directory (where you first issue the cmake command)?

Yes, of course I did. I do all my compiling things locally. I don't issue cmake command, I let Qt Creator make it:

cmake -G "Unix Makefiles" -DCMAKE_INSTALL_PREFIX=/home/varlog/gits/Sigil-build -DCMAKE_BUILD_TYPE=Debug /home/varlog/gits/Sigil -DCMAKE_PREFIX_PATH=/opt/Qt5.3.1/5.3/gcc_64/lib/cmake

it works as promised! only /share doesn't.

[KevinH]

Hi,
The relevant CMake file shows the following for Linux:

install( FILES ${PLUGIN_FILES_PYTHON} DESTINATION ${CMAKE_INSTALL_PREFIX}/share/sigil/plugin_launchers/python/ )

So as long as Linux install defaults to create any missing directories in the path, this should work.
To test, simply create the required directories manually first and then see if it is properly populated. If so, then "install" might need to have -d added to it. But then the other directories used should have the same problems so I am guessing here.

KevinH

[varlog]

Originally Posted by KevinH

Hi,
The relevant CMake file shows the following for Linux:

install( FILES ${PLUGIN_FILES_PYTHON} DESTINATION ${CMAKE_INSTALL_PREFIX}/share/sigil/plugin_launchers/python/ )

So as long as Linux install defaults to create any missing directories in the path, this should work.
To test, simply create the required directories manually first and then see if it is properly populated. If so, then "install" might need to have -d added to it. But then the other directories used should have the same problems so I am guessing here.

KevinH

yes, I've seen "install( FILES ${PLUGIN_FILES_PYTHON} DESTINATION ${CMAKE_INSTALL_PREFIX}/share/sigil/plugin_launchers/python/ )" in CMakeList.txt... I'm trying with folders created... nope .

[DiapDealer]

After Qt Creator builds the project, how does it get installed? Those files in the install prefix won't get created unless something actually issues the "make install" command. That folder structure doesn't get created in the normal build phase.

Just pulled a fresh copy from github, and all I can say is ... everything works as expected using the cmake, make, make install process. All files are copied to my install prefix--whether using the default /usr/local or specifying a custom one with -DCMAKE_INSTALL_PREFIX.

[varlog]

Originally Posted by DiapDealer

After Qt Creator builds the project, how does it get installed? Those files in the install prefix won't get created unless something actually issues the "make install" command. That folder structure doesn't get created in the normal build phase.

Just pulled a fresh copy from github, and all I can say is ... everything works as expected using the cmake, make, make install process. All files are copied to my install prefix--whether using the default /usr/local or specifying a custom one with -DCMAKE_INSTALL_PREFIX.

hmm, interesting... there is this:

if( UNIX AND NOT APPLE )
    install( TARGETS ${PROJECT_NAME} RUNTIME DESTINATION ${CMAKE_INSTALL_PREFIX}/bin/ )
    install( FILES ${LINUX_DESKTOP_FILE} DESTINATION ${CMAKE_INSTALL_PREFIX}/share/applications/ )
    install( FILES ${LINUX_DESKTOP_ICON_FILE} DESTINATION ${CMAKE_INSTALL_PREFIX}/share/pixmaps RENAME sigil.png )
    install( FILES ${QM_FILES} DESTINATION ${CMAKE_INSTALL_PREFIX}/share/sigil/translations/ )
    install( FILES ${DIC_FILES} DESTINATION ${CMAKE_INSTALL_PREFIX}/share/sigil/hunspell_dictionaries/ )
    install( FILES ${PLUGIN_FILES_PYTHON} DESTINATION ${CMAKE_INSTALL_PREFIX}/share/sigil/plugin_launchers/python/ )
    install( FILES ${EXAMPLE_FILES} DESTINATION ${CMAKE_INSTALL_PREFIX}/share/sigil/examples/ )
endif()

in CMakeList.txt.
bin/ is created, lib/ is there...(?!) share/ is not. Qt Creator bug?

will try it manually - but not today...

[user_none]

Originally Posted by varlog

hmm, interesting... there is this:
...
in CMakeList.txt.
bin/ is created, lib/ is there...(?!) share/ is not. Qt Creator bug?

Did you manually run "make install" ?

QtCreator will not run that for you by default when you build. You must run "make install" for that section to apply. The lib and build directories are created by the build process for the build.

Install is a different target. The bin and lib dirs in the install target are completely different. You should not install into your build dir root either. You'll run into all kinds of problems because you're going to have files in bin trying to be installed into bin. Use a dir under build like "inst" as your install target.

[DiapDealer]

Originally Posted by varlog

hmm, interesting... there is this:

Yes. That's the entirety of what creates the "install" make target.

bin/ is created, lib/ is there...(?!) share/ is not. Qt Creator bug?

Not sure. Never really been tempted to use it, to tell the truth. By the time I figure out how to create a new project and get all the options set correctly, I could already be done with manual compile process and be playing with the program.

EDIT: I see user_none has already determined that Qt Creator does not issue the make install command.

[varlog]

Originally Posted by user_none

Did you manually run "make install" ?

QtCreator will not run that for you by default when you build. You must run "make install" for that section to apply. The lib and build directories are created by the build process for the build.

Install is a different target. The bin and lib dirs in the install target are completely different. You should not install into your build dir root either. You'll run into all kinds of problems because you're going to have files in bin trying to be installed into bin. Use a dir under build like "inst" as your install target.

must have been obvious, humm? thanks.

[varlog]

Originally Posted by DiapDealer

Not sure. Never really been tempted to use it, to tell the truth. By the time I figure out how to create a new project and get all the options set correctly, I could already be done with manual compile process and be playing with the program.

I can only say that without Qt Creator I won't be doing it at all. Very nice development environment for Qt.

[user_none]

Originally Posted by varlog

I can only say that without Qt Creator I won't be doing it at all. Very nice development environment for Qt.

Vim is all you need ;-).