FAQ

From VLE

Compilation

A specific page for compilation errors.

GVLE

Open a text file with gvle: encoding error

If you get this type of error: This file isn't UTF-8 valid. Please convert this file with your source code editor it is probably because the text editor embedded in gvle exclusively uses the UTF-8 encoding. Please, convert your file using your preferred text editor software or one of the following good solutions.

• vim, gvim (Windows & Linux), open one or several files and write on the command line:

" file conversion precessing"
:set fileencoding=utf-8
:w
 
" convert all open buffers"
:argdo :set fileencoding=utf-8 | update

• iconv (Linux) a specialized command to automatize the conversion process (two examples):

# To convert the cpp file:
iconv -t utf-8 model.cpp -o model.cpp.utf8
mv model.cpp.utf8 model.cpp
 
# To convert several cpp files:
ls *.cpp | xargs -t -i bash -c "iconv -t utf-8 {} -o {}.utf8 ; mv {}.utf8 {}"

Issues by OS

Linux

Link edition error while running VLE or GLVE

If, after the installation of the Deb or the RPM package for VLE, you note that one of the dynamic libraries is not available (for instance: libboost-filesystem-1.34.1.so), it means that the binary package we provide is not compatible with your OS. If the missing library is not available in the good version for your OS, we advice you to compile sources of VLE on your OS.

Windows

Installing a new version of VLE: error detecting Boost

If you have an arror related to the Boost library after the installation of VLE for Windows, it is probably because you have already another version of VLE installed. It is not recommended to install two different version of VLE. If you really want several version of VLE, you have to modify environment variables by hand i.e. delete references to the old version and keep the new ones for the 4 following variables: BOOST_ROOT, BOOST_INCLUDEDIR, BOOST_LIBRARYDIR et PKG_CONFIG_PATH.

Using the the standard output stream and GVLE

If you want to print to a console messages, just do it by the regular way by inserting inside your own code line like this:

std::cout << " a debug message" <<std::endl;

Then you will have to get the Windows command line, and launch gvle either like this

C:\Documents an Settings\me>gvle > mylogfile

in order to get all the messages inside the "mylogfile" file. Or you can launch gvle like this:

C:\Documents an Settings\me>gvle | more

in order to see the messages directly on the terminal, by using the "more" command coming with MinGW.

Langues :

English  • Français