Nabble - Gnu - Source Highlight

Re: Compilation failures using qmake + mingw / msvc

2009-11-19T13:41:11Z

so the test.cpp example which is in the same directory of the pro file
seems to work right?

Forgive me if I say something obvious, but do you run qmake with
-recursive? And, most of all, these

debug: LIBS += -Llib/boost/regex/mingw/debug
-llibboost_regex-mgw34-mt-d-1_40

release:LIBS += -Llib/boost/regex/mingw/release
-llibboost_regex-mgw34-mt-1_40

INCLUDEPATH +=
H:/matthias/Documents/Dev/CPP/SVN/library/source/boost_1_40_0/

should be visible in the subdirectories' pro files, and this does not
happen automatic;

thus, either you add these specifications in the defines.pri (which is
automatically included in the subdirectories' pro files), or you specify
this values on the command line when running qmake (and you also specify
-recursive).

is this your case?

cheers
Lorenzo

Matthias Pospiech wrote:

> If I compile your library with this code inserted in the main .pro file
> it does not include the boost path during compilation:
>
> debug: LIBS += -Llib/boost/regex/mingw/debug
> -llibboost_regex-mgw34-mt-d-1_40
>
> release:LIBS += -Llib/boost/regex/mingw/release
> -llibboost_regex-mgw34-mt-1_40
>
> INCLUDEPATH +=
> H:/matthias/Documents/Dev/CPP/SVN/library/source/boost_1_40_0/
>
>
> which means it fails as before.
>
>
>
> However I can compile and link the boost example successfully using this
> qmake code:
> (which is the same as above, just more code for the destination of files)
>
> CONFIG += release
>
> CONFIG -= debug
>
> CONFIG -= qt
>
> CONFIG += thread warn_on
>
> TEMPLATE = app
>
> TARGET = test
>
> # -------------------------------------------------
>
> # Define Variables
>
> # -------------------------------------------------
>
> BUILD_DIR = build
>
> BIN_DIR = bin
>
> # -------------------------------------------------
>
> # Target Directory
>
> # -------------------------------------------------
>
> debug:DESTDIR = $${BIN_DIR}/mingw/debug/
>
> release:DESTDIR = $${BIN_DIR}/mingw/release/
>
> # -------------------------------------------------
>
> # Objects Directory
>
> # -------------------------------------------------
>
> debug{
>
> OBJECTS_DIR = $${BUILD_DIR}/$${BINARY_NAME}/debug/
>
> }
>
> release{
>
> OBJECTS_DIR = $${BUILD_DIR}/$${BINARY_NAME}/release/
>
> }
>
> # -------------------------------------------------
>
> # Include directories
>
> # -------------------------------------------------
>
> INCLUDEPATH +=
> H:/matthias/Documents/Dev/CPP/SVN/library/source/boost_1_40_0/
>
> # -------------------------------------------------
>
> # Libaries
>
> # -------------------------------------------------
>
> debug: LIBS += -Llib/boost/regex/mingw/debug
> -llibboost_regex-mgw34-mt-d-1_40
>
> release:LIBS += -Llib/boost/regex/mingw/release
> -llibboost_regex-mgw34-mt-1_40
>
> # -------------------------------------------------
>
> # Sources
>
> # -------------------------------------------------
>
> SOURCES += test.cpp
>
>
>
> so somewhere in the qmake code of your library the INCLUDEPATH is
> overwritten is assume.
>
> Best Regards,
> Matthias

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: Compilation failures using qmake + mingw / msvc

2009-11-19T13:11:33Z

If I compile your library with this code inserted in the main .pro file
it does not include the boost path during compilation:

debug: LIBS += -Llib/boost/regex/mingw/debug
-llibboost_regex-mgw34-mt-d-1_40

release:LIBS += -Llib/boost/regex/mingw/release
-llibboost_regex-mgw34-mt-1_40

INCLUDEPATH +=
H:/matthias/Documents/Dev/CPP/SVN/library/source/boost_1_40_0/

which means it fails as before.

However I can compile and link the boost example successfully using this
qmake code:
(which is the same as above, just more code for the destination of files)

CONFIG += release

CONFIG -= debug

CONFIG -= qt

CONFIG += thread warn_on

TEMPLATE = app

TARGET = test

# -------------------------------------------------

# Define Variables

# -------------------------------------------------

BUILD_DIR = build

BIN_DIR = bin

# -------------------------------------------------

# Target Directory

# -------------------------------------------------

debug:DESTDIR = $${BIN_DIR}/mingw/debug/

release:DESTDIR = $${BIN_DIR}/mingw/release/

# -------------------------------------------------

# Objects Directory

# -------------------------------------------------

debug{

OBJECTS_DIR = $${BUILD_DIR}/$${BINARY_NAME}/debug/

}

release{

OBJECTS_DIR = $${BUILD_DIR}/$${BINARY_NAME}/release/

}

# -------------------------------------------------

# Include directories

# -------------------------------------------------

INCLUDEPATH +=
H:/matthias/Documents/Dev/CPP/SVN/library/source/boost_1_40_0/

# -------------------------------------------------

# Libaries

# -------------------------------------------------

debug: LIBS += -Llib/boost/regex/mingw/debug
-llibboost_regex-mgw34-mt-d-1_40

release:LIBS += -Llib/boost/regex/mingw/release
-llibboost_regex-mgw34-mt-1_40

# -------------------------------------------------

# Sources

# -------------------------------------------------

SOURCES += test.cpp

so somewhere in the qmake code of your library the INCLUDEPATH is
overwritten is assume.

Best Regards,
Matthias

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: Compilation failures using qmake + mingw / msvc

2009-11-19T10:34:52Z

Lorenzo Bettini wrote:

> Lorenzo Bettini wrote:
>> Here you find the version I've been working on this evening under
>> mingw/windows
>>
>> http://gdn.dsi.unifi.it/~bettini/binaries/source-highlight-qmake-3.1.2.tar.gz
>>
>>
>> and it solves the errors with mkdir and other things.
>>
>> For the moment, use CONFIG+=static and do not build dll (since they
>> use a different naming and it still has to be tweaked a little bit,
>> not to mention that I know exceptions across dlls do not work well...).
>>
>
> oh, and I forgot:
>
> make sure to run qmake passing USE_MINGW=1 so that it solves the problem
> with mkdir.
>
> cheers
> Lorenzo
>

Another thing: use this modified version of defines.pri (which sets
CONFIG += console), otherwise no output is shown on stdout on windows (I
was about to go mad about that, since I couldn't really figure out what
was happening ;)

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

VERSION = 3.0.1

CONFIG -= qt
CONFIG += console

DEFINES += ABSOLUTEDATADIR=\\\"/usr/local/share/source-highlight/\\\" \
VERSION=\\\"3.1.2\\\" \
LIBRARY_VERSION=\\\"3.0.0\\\" \
PACKAGE=\\\"source-highlight\\\" \
RELATIVEDATADIR=\\\"../share/source-highlight\\\"

LIBRARY_NAME = source-highlight

ADDITIONAL_LIBRARIES = -lboost_regex

#!isEmpty(USE_MINGW) {
#LIBRARY_LIB = $${LIBRARY_NAME}3
#} else {
LIBRARY_LIB = $${LIBRARY_NAME}
#}

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: Compilation failures using qmake + mingw / msvc

2009-11-18T16:01:45Z

Lorenzo Bettini wrote:

> Here you find the version I've been working on this evening under
> mingw/windows
>
> http://gdn.dsi.unifi.it/~bettini/binaries/source-highlight-qmake-3.1.2.tar.gz
>
>
> and it solves the errors with mkdir and other things.
>
> For the moment, use CONFIG+=static and do not build dll (since they use
> a different naming and it still has to be tweaked a little bit, not to
> mention that I know exceptions across dlls do not work well...).
>

oh, and I forgot:

make sure to run qmake passing USE_MINGW=1 so that it solves the problem
with mkdir.

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: Compilation failures using qmake + mingw / msvc

2009-11-18T15:35:38Z

Here you find the version I've been working on this evening under
mingw/windows

http://gdn.dsi.unifi.it/~bettini/binaries/source-highlight-qmake-3.1.2.tar.gz

and it solves the errors with mkdir and other things.

For the moment, use CONFIG+=static and do not build dll (since they use
a different naming and it still has to be tweaked a little bit, not to
mention that I know exceptions across dlls do not work well...).

cheers
Lorenzo

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: Compilation failures using qmake + mingw / msvc

2009-11-18T15:30:00Z

Lorenzo Bettini wrote:

> Matthias Pospiech wrote:
>> Lorenzo Bettini schrieb:
>>> Matthias Pospiech wrote:
>>>> Lorenzo Bettini schrieb:
>>>>> Matthias Pospiech wrote:
>>>>>> Lorenzo Bettini schrieb:
>>>>>>>
>>>>>>> P.S. it looks like building boost with msvc is fully supported:
>>>>>>> http://www.boost.org/doc/libs/1_41_0/more/getting_started/windows.html
>>>>>>>
>>>>>>>
>>>>>> building boost is not a problem, I have a problem to tell qmake
>>>>>> where the include files are, since it does not find them.
>>>>>
>>>>> you should pass to qmake these options
>>>>>
>>>>> INCPATH+="/usr/local/include" LIBS+="-L/usr/local/lib -lboost_regex"
>>>>>
>>>> I am not using linux, so it reads
>>>>
>>>> debug: LIBS += -Llib/boost/regex/mingw/debug
>>>> -lboost_regex-mgw34-mt-d-1_40
>>>> release:LIBS += -Llib/boost/regex/mingw/release
>>>> -lboost_regex-mgw34-mt-1_40
>>>>
>>>
>>> yes, it's the same, I just meant that instead of polluting the .pro
>>> file you can pass these options to qmake at the command line :)
>>>
>>>> note that I copy the library file to a new location, because the
>>>> compilation destination path of boost is very strange.
>>>>
>>>> The include is added via
>>>>
>>>> INCLUDEPATH += ../boost_1_40_0
>>>>
>>>> or the full path. However during compilation the boost library
>>>> headers are not found.
>>>
>>> you have to put in the INCLUDEPATH (which I usually write as INCPATH,
>>> are you sure it's the same?) the path where the boost subdirectory is.
>>>
>>> For instance, if regex.hpp is in
>>>
>>> /my/path/boost_1_40_0/include/boost
>>>
>>> then you need to specify as include path
>>>
>>> /my/path/boost_1_40_0/include/
>>>
>>> since boost header files are included as follows
>>>
>>> #include <boost/regex.hpp>
>>>
>>> As for the compilation and installation of boost you can still refer
>>> to that blog post since those flags are for bootstrap and bjam anyway.
>>>
>> I understand the path-thing. In my case the file regex.hpp is in
>> H:\matthias\Documents\Dev\CPP\SVN\library\source\boost_1_40_0\boost
>>
>> which is why have set up
>> INCLUDEPATH +=
>> H:/matthias/Documents/Dev/CPP/SVN/library/source/boost_1_40_0/
>>
>> but that does not work. The error in qtcreator is:
>>
>> H:/matthias/Documents/Dev/CPP/SVN/library/source/source-highlight-3.1.2/lib/srchilite/substfun.h:13:
>> boost/regex.hpp: No such file or directory
>>
>>
>> The compilation output however does not include this path, which I do
>> not understand:
>> g++ -c -g -frtti -fexceptions -mthreads -Wall
>> -DABSOLUTEDATADIR=\"/usr/local/share/source-highlight/\"
>> -DVERSION=\"3.1.2\" -DLIBRARY_VERSION=\"3.0.0\"
>> -DPACKAGE=\"source-highlight\"
>> -DRELATIVEDATADIR=\"../share/source-highlight\" -DQT_DLL -DQT_GUI_LIB
>> -DQT_CORE_LIB -DQT_THREAD_SUPPORT
>> -I'c:/Programme/Qt/SDK/2009.04/qt/include/QtCore'
>> -I'c:/Programme/Qt/SDK/2009.04/qt/include/QtGui'
>> -I'c:/Programme/Qt/SDK/2009.04/qt/include'
>> -I'c:/Programme/Qt/SDK/2009.04/qt/include/ActiveQt' -I'debug'
>> -I'c:/Programme/Qt/SDK/2009.04/qt/mkspecs/win32-g++' -o
>> debug/substfun.o substfun.cpp
>

and sorry if I insist on this, but you should try with the simple
example of regexp

#include <boost/regex.hpp>
#include <iostream>
#include <string>

int main()
{
std::string line;
boost::regex pat( "^Subject: (Re: |Aw: )*(.*)" );

while (std::cin)
{
std::getline(std::cin, line);
boost::smatch matches;
if (boost::regex_match(line, matches, pat))
std::cout << matches[2] << std::endl;
}
}

in a single file (mytest.cpp) and compile it manually with the -I and -L

g++ -IH:/matthias/Documents/Dev/CPP/SVN/library/source/boost_1_40_0/
mytest.cpp -o mytest
-LH:/matthias/Documents/Dev/CPP/SVN/library/source/boost_1_40_0/lib
-lboost_regex

otherwise you might not understand what is going wrong... :)

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: Compilation failures using qmake + mingw / msvc

2009-11-18T15:20:14Z

Matthias Pospiech wrote:

> Lorenzo Bettini schrieb:
>> Matthias Pospiech wrote:
>>> Lorenzo Bettini schrieb:
>>>> Matthias Pospiech wrote:
>>>>> Lorenzo Bettini schrieb:
>>>>>>
>>>>>> P.S. it looks like building boost with msvc is fully supported:
>>>>>> http://www.boost.org/doc/libs/1_41_0/more/getting_started/windows.html
>>>>>>
>>>>>>
>>>>> building boost is not a problem, I have a problem to tell qmake
>>>>> where the include files are, since it does not find them.
>>>>
>>>> you should pass to qmake these options
>>>>
>>>> INCPATH+="/usr/local/include" LIBS+="-L/usr/local/lib -lboost_regex"
>>>>
>>> I am not using linux, so it reads
>>>
>>> debug: LIBS += -Llib/boost/regex/mingw/debug
>>> -lboost_regex-mgw34-mt-d-1_40
>>> release:LIBS += -Llib/boost/regex/mingw/release
>>> -lboost_regex-mgw34-mt-1_40
>>>
>>
>> yes, it's the same, I just meant that instead of polluting the .pro
>> file you can pass these options to qmake at the command line :)
>>
>>> note that I copy the library file to a new location, because the
>>> compilation destination path of boost is very strange.
>>>
>>> The include is added via
>>>
>>> INCLUDEPATH += ../boost_1_40_0
>>>
>>> or the full path. However during compilation the boost library
>>> headers are not found.
>>
>> you have to put in the INCLUDEPATH (which I usually write as INCPATH,
>> are you sure it's the same?) the path where the boost subdirectory is.
>>
>> For instance, if regex.hpp is in
>>
>> /my/path/boost_1_40_0/include/boost
>>
>> then you need to specify as include path
>>
>> /my/path/boost_1_40_0/include/
>>
>> since boost header files are included as follows
>>
>> #include <boost/regex.hpp>
>>
>> As for the compilation and installation of boost you can still refer
>> to that blog post since those flags are for bootstrap and bjam anyway.
>>
> I understand the path-thing. In my case the file regex.hpp is in
> H:\matthias\Documents\Dev\CPP\SVN\library\source\boost_1_40_0\boost
>
> which is why have set up
> INCLUDEPATH +=
> H:/matthias/Documents/Dev/CPP/SVN/library/source/boost_1_40_0/
>
> but that does not work. The error in qtcreator is:
>
> H:/matthias/Documents/Dev/CPP/SVN/library/source/source-highlight-3.1.2/lib/srchilite/substfun.h:13:
> boost/regex.hpp: No such file or directory
>
>
> The compilation output however does not include this path, which I do
> not understand:
> g++ -c -g -frtti -fexceptions -mthreads -Wall
> -DABSOLUTEDATADIR=\"/usr/local/share/source-highlight/\"
> -DVERSION=\"3.1.2\" -DLIBRARY_VERSION=\"3.0.0\"
> -DPACKAGE=\"source-highlight\"
> -DRELATIVEDATADIR=\"../share/source-highlight\" -DQT_DLL -DQT_GUI_LIB
> -DQT_CORE_LIB -DQT_THREAD_SUPPORT
> -I'c:/Programme/Qt/SDK/2009.04/qt/include/QtCore'
> -I'c:/Programme/Qt/SDK/2009.04/qt/include/QtGui'
> -I'c:/Programme/Qt/SDK/2009.04/qt/include'
> -I'c:/Programme/Qt/SDK/2009.04/qt/include/ActiveQt' -I'debug'
> -I'c:/Programme/Qt/SDK/2009.04/qt/mkspecs/win32-g++' -o debug/substfun.o
> substfun.cpp

have you written INCLUDEPATH in the .pro file? Or are you passing it to
qmake at the command line?

Please, also try with INCPATH instead of INCLUDEPATH.

cheers
Lorenzo

P.S. at least this is not my fault, but qmake's one ;)

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: Compilation failures using qmake + mingw / msvc

2009-11-18T14:26:33Z

Lorenzo Bettini schrieb:

> Matthias Pospiech wrote:
>> Lorenzo Bettini schrieb:
>>> Matthias Pospiech wrote:
>>>> Lorenzo Bettini schrieb:
>>>>>
>>>>> P.S. it looks like building boost with msvc is fully supported:
>>>>> http://www.boost.org/doc/libs/1_41_0/more/getting_started/windows.html
>>>>>
>>>>>
>>>> building boost is not a problem, I have a problem to tell qmake
>>>> where the include files are, since it does not find them.
>>>
>>> you should pass to qmake these options
>>>
>>> INCPATH+="/usr/local/include" LIBS+="-L/usr/local/lib -lboost_regex"
>>>
>> I am not using linux, so it reads
>>
>> debug: LIBS += -Llib/boost/regex/mingw/debug
>> -lboost_regex-mgw34-mt-d-1_40
>> release:LIBS += -Llib/boost/regex/mingw/release
>> -lboost_regex-mgw34-mt-1_40
>>
>
> yes, it's the same, I just meant that instead of polluting the .pro
> file you can pass these options to qmake at the command line :)
>
>> note that I copy the library file to a new location, because the
>> compilation destination path of boost is very strange.
>>
>> The include is added via
>>
>> INCLUDEPATH += ../boost_1_40_0
>>
>> or the full path. However during compilation the boost library
>> headers are not found.
>
> you have to put in the INCLUDEPATH (which I usually write as INCPATH,
> are you sure it's the same?) the path where the boost subdirectory is.
>
> For instance, if regex.hpp is in
>
> /my/path/boost_1_40_0/include/boost
>
> then you need to specify as include path
>
> /my/path/boost_1_40_0/include/
>
> since boost header files are included as follows
>
> #include <boost/regex.hpp>
>
> As for the compilation and installation of boost you can still refer
> to that blog post since those flags are for bootstrap and bjam anyway.
>

I understand the path-thing. In my case the file regex.hpp is in
H:\matthias\Documents\Dev\CPP\SVN\library\source\boost_1_40_0\boost

which is why have set up
INCLUDEPATH +=
H:/matthias/Documents/Dev/CPP/SVN/library/source/boost_1_40_0/

but that does not work. The error in qtcreator is:

H:/matthias/Documents/Dev/CPP/SVN/library/source/source-highlight-3.1.2/lib/srchilite/substfun.h:13:
boost/regex.hpp: No such file or directory

The compilation output however does not include this path, which I do
not understand:
g++ -c -g -frtti -fexceptions -mthreads -Wall
-DABSOLUTEDATADIR=\"/usr/local/share/source-highlight/\"
-DVERSION=\"3.1.2\" -DLIBRARY_VERSION=\"3.0.0\"
-DPACKAGE=\"source-highlight\"
-DRELATIVEDATADIR=\"../share/source-highlight\" -DQT_DLL -DQT_GUI_LIB
-DQT_CORE_LIB -DQT_THREAD_SUPPORT
-I'c:/Programme/Qt/SDK/2009.04/qt/include/QtCore'
-I'c:/Programme/Qt/SDK/2009.04/qt/include/QtGui'
-I'c:/Programme/Qt/SDK/2009.04/qt/include'
-I'c:/Programme/Qt/SDK/2009.04/qt/include/ActiveQt' -I'debug'
-I'c:/Programme/Qt/SDK/2009.04/qt/mkspecs/win32-g++' -o debug/substfun.o
substfun.cpp

Matthias

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: Compilation failures using qmake + mingw / msvc

2009-11-18T13:00:41Z

Matthias Pospiech wrote:

> Lorenzo Bettini schrieb:
>> Matthias Pospiech wrote:
>>> Lorenzo Bettini schrieb:
>>>>
>>>> P.S. it looks like building boost with msvc is fully supported:
>>>> http://www.boost.org/doc/libs/1_41_0/more/getting_started/windows.html
>>>>
>>> building boost is not a problem, I have a problem to tell qmake where
>>> the include files are, since it does not find them.
>>
>> you should pass to qmake these options
>>
>> INCPATH+="/usr/local/include" LIBS+="-L/usr/local/lib -lboost_regex"
>>
> I am not using linux, so it reads
>
> debug: LIBS += -Llib/boost/regex/mingw/debug
> -lboost_regex-mgw34-mt-d-1_40
> release:LIBS += -Llib/boost/regex/mingw/release
> -lboost_regex-mgw34-mt-1_40
>

yes, it's the same, I just meant that instead of polluting the .pro file
you can pass these options to qmake at the command line :)

> note that I copy the library file to a new location, because the
> compilation destination path of boost is very strange.
>
> The include is added via
>
> INCLUDEPATH += ../boost_1_40_0
>
> or the full path. However during compilation the boost library headers
> are not found.

you have to put in the INCLUDEPATH (which I usually write as INCPATH,
are you sure it's the same?) the path where the boost subdirectory is.

For instance, if regex.hpp is in

/my/path/boost_1_40_0/include/boost

then you need to specify as include path

/my/path/boost_1_40_0/include/

since boost header files are included as follows

#include <boost/regex.hpp>

As for the compilation and installation of boost you can still refer to
that blog post since those flags are for bootstrap and bjam anyway.

please let me know

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: Compilation failures using qmake + mingw / msvc

2009-11-18T12:43:54Z

Lorenzo Bettini schrieb:

> Matthias Pospiech wrote:
>> Lorenzo Bettini schrieb:
>>>
>>> P.S. it looks like building boost with msvc is fully supported:
>>> http://www.boost.org/doc/libs/1_41_0/more/getting_started/windows.html
>>>
>> building boost is not a problem, I have a problem to tell qmake where
>> the include files are, since it does not find them.
>
> you should pass to qmake these options
>
> INCPATH+="/usr/local/include" LIBS+="-L/usr/local/lib -lboost_regex"
>

I am not using linux, so it reads

debug: LIBS += -Llib/boost/regex/mingw/debug
-lboost_regex-mgw34-mt-d-1_40
release:LIBS += -Llib/boost/regex/mingw/release
-lboost_regex-mgw34-mt-1_40

note that I copy the library file to a new location, because the
compilation destination path of boost is very strange.

The include is added via

INCLUDEPATH += ../boost_1_40_0

or the full path. However during compilation the boost library headers
are not found.

Matthias

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: Compilation failures using qmake + mingw / msvc

2009-11-18T11:57:20Z

Matthias Pospiech wrote:
> Lorenzo Bettini schrieb:
>>
>> P.S. it looks like building boost with msvc is fully supported:
>> http://www.boost.org/doc/libs/1_41_0/more/getting_started/windows.html
>>
> building boost is not a problem, I have a problem to tell qmake where
> the include files are, since it does not find them.

you should pass to qmake these options

INCPATH+="/usr/local/include" LIBS+="-L/usr/local/lib -lboost_regex"

depending on where you installed boost; where have you installed them?
In particular the headers and the lib?

you may want to try with a simpler example first (see, e.g., the example
here:
http://tronprog.blogspot.com/2009/10/compiling-boost-regex-in-linux.html)

and run g++ with the -I and -L options.

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: Compilation failures using qmake + mingw / msvc

2009-11-18T10:46:28Z

Lorenzo Bettini schrieb:
>
> P.S. it looks like building boost with msvc is fully supported:
> http://www.boost.org/doc/libs/1_41_0/more/getting_started/windows.html
>
building boost is not a problem, I have a problem to tell qmake where
the include files are, since it does not find them.

Matthias

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: Compilation failures using qmake + mingw / msvc

2009-11-18T09:36:23Z

Matthias Pospiech wrote:

> Lorenzo Bettini schrieb:
>> Lorenzo Bettini wrote:
>>> Hi
>>>
>>> I'm working on this, and solving the autoconf generated files and
>>> defines in the .pro files, it's taking me some time.
>>>
>>> Hope to have something ready soon :)
>>>
>>
>> OK, I made it, at least I can successfully build both source-highlight
>> and source-highlight-qt under Linux with qmake, you can find these
>> source tar balls here:
>>
>> http://gdn.dsi.unifi.it/~bettini/binaries/source-highlight-qmake-3.1.2.tar.gz
>>
>> http://gdn.dsi.unifi.it/~bettini/binaries/source-highlight-qt-qmake-0.2.tar.gz
>>
>>
>> I still haven't tried that on windows 'cause I need some sleep now :)
>>
> I have not included the regex libs, since they have a very long and
> compiler specific name which is not included in your .pro file so far.
> However I tried to compile it to see if it finishes that step:
>
> Here the errors that come with msvc: (I leave out the warnings)
>
> .\stylescanner.cc(621) : fatal error C1083: Datei (Include) kann nicht
> geöffnet werden: "unistd.h": No such file or directory

by looking at that file (which is automatically generated by flex) I see

#ifndef YY_NO_UNISTD_H
/* Special case for "unistd.h", since it is non-ANSI. We include it way
* down here because we want the user's section 1 to have been scanned
first.
* The user has a chance to override it with an option.
*/
#include <unistd.h>
#endif

thus it's possible to avoid to include unistd.h by adding

DEFINES += YY_NO_UNISTD_H

either in the .pro file, or, better to qmake command line; would you
please try this?

thanks
Lorenzo

P.S. it looks like building boost with msvc is fully supported:
http://www.boost.org/doc/libs/1_41_0/more/getting_started/windows.html

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: Compilation failures using qmake + mingw / msvc

2009-11-18T08:41:44Z

Matthias Pospiech wrote:

you can pass this information to qmake with (I'm writing without being
to verify that)

INCPATH+="/usr/local/include" LIBS+="-L/usr/local/lib -lboost_regex"

if you extracted that tar ball in c:

> However I tried to compile it to see if it finishes that step:
>
> Here the errors that come with msvc: (I leave out the warnings)
>
> .\stylescanner.cc(621) : fatal error C1083: Datei (Include) kann nicht
> geöffnet werden: "unistd.h": No such file or directory
>
> This is a Unix only file which is is emulated by mingw, but not existend
> in other compilers which means that it is not available for msvc.
>

mh... I see what I can do about that, but I don't know whether I can do
something... note that the configure based system is able to deal with
that but I don't know how to adapt that to msvc

> With mingw it compiles until it complains that boost is not found. This
> is something I have to solve before.

have you tried this site providing builds of boost regex for mingw?
http://nuwen.net/mingw.html

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: Compilation failures using qmake + mingw / msvc

2009-11-18T07:55:22Z

Lorenzo Bettini schrieb:

> Lorenzo Bettini wrote:
>> Hi
>>
>> I'm working on this, and solving the autoconf generated files and
>> defines in the .pro files, it's taking me some time.
>>
>> Hope to have something ready soon :)
>>
>
> OK, I made it, at least I can successfully build both source-highlight
> and source-highlight-qt under Linux with qmake, you can find these
> source tar balls here:
>
> http://gdn.dsi.unifi.it/~bettini/binaries/source-highlight-qmake-3.1.2.tar.gz
>
> http://gdn.dsi.unifi.it/~bettini/binaries/source-highlight-qt-qmake-0.2.tar.gz
>
>
> I still haven't tried that on windows 'cause I need some sleep now :)
>

I have not included the regex libs, since they have a very long and
compiler specific name which is not included in your .pro file so far.
However I tried to compile it to see if it finishes that step:

Here the errors that come with msvc: (I leave out the warnings)

.\stylescanner.cc(621) : fatal error C1083: Datei (Include) kann nicht
geöffnet werden: "unistd.h": No such file or directory

This is a Unix only file which is is emulated by mingw, but not existend
in other compilers which means that it is not available for msvc.

With mingw it compiles until it complains that boost is not found. This
is something I have to solve before.

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: Compilation failures using qmake + mingw / msvc

2009-11-17T15:30:19Z

Lorenzo Bettini wrote:
> Hi
>
> I'm working on this, and solving the autoconf generated files and
> defines in the .pro files, it's taking me some time.
>
> Hope to have something ready soon :)
>

OK, I made it, at least I can successfully build both source-highlight
and source-highlight-qt under Linux with qmake, you can find these
source tar balls here:

http://gdn.dsi.unifi.it/~bettini/binaries/source-highlight-qmake-3.1.2.tar.gz
http://gdn.dsi.unifi.it/~bettini/binaries/source-highlight-qt-qmake-0.2.tar.gz

I still haven't tried that on windows 'cause I need some sleep now :)

Note that you still need to rely on boost_regex, so make sure it's in
your path or at least use INCPATH and LIBS appropriately when running
qmake (you might want to reuse the binary version of boost_regex lib and
related include in the binary package I built yesterday).

As for the installation, the same directory layout is used, but of
course you can tweak it with

INSTALL_ROOT=<myroot> make install

Of course, install source-highlight first, and then build and install
source-highlight-qt accordingly.

Please, try this on windows (I'll try that tomorrow), and you might
probably have to pass some other arguments to qmake to use it with msvc
(as I said I don't have that).

We'll probably have to deal with some warnings msvc will issue (I guess).

In any case, I strongly suggest you not to build them with dll (use
CONFIG+=static), at least as a first attempt.

If you modify the .pro files, please use conditionals in there (and
please send them back to me).

IMPORTANT: as for now, source-highlight comes with an hardcoded path for
searching for its lang files (and other files):
/usr/local/share/source-highlight, so you might want to install it using
the prefix /usr/local:

INSTALL_ROOT=/usr/local make install

If you install it in a different root path, then, remember to run
source-highlight-settings first so that you can specify a different data
path (and it will store it in your personal configuration for you, once
and for all).

hope to hear from you soon
good night
Lorenzo

P.S. I've been thinking for a long time to provide a conditional
compilation strategy so that source-highlight itself can use QRegExp
instead of boost regex, but this will require some more work (and
reengineering of some parts of source-highlight) and I cannot do that
immediately. :)

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: Compilation failures using qmake + mingw / msvc

2009-11-17T14:18:39Z

Hi

I'm working on this, and solving the autoconf generated files and
defines in the .pro files, it's taking me some time.

Hope to have something ready soon :)

cheers
Lore

Matthias Pospiech wrote:

> I have set up a qmake .pro file to make the libary without autoconf.
> (file attached)
>
> You will see in the following issues, that moving away from autoconf and
> to windows problems
> arise that indicate that the code could be improved in its plattform
> independence.
> So I do not want to complain that it fails compilation, but want to give
> hints to improve the
> plattform independence.
>
> Using mingw I run into the following issues:
>
> /source-highlight-3.1/lib/srchilite/settings.cpp:11: config.h: No such
> file or directory
> /source-highlight-3.1/lib/srchilite/settings.cpp:37: error:
> `ABSOLUTEDATADIR' was not declared in this scope
> C:/Programme/Qt/SDK/2009.04/mingw/bin/../lib/gcc/mingw32/3.4.5/../../../../include/io.h:176:
> error: too many arguments to function `int mkdir(const char*)'
> /source-highlight-3.1/lib/srchilite/settings.cpp:90: error: at this
> point in file
>
> so that complition is stopped at settings.cpp.
>
> Compling with msvc-2005 is more problematic:
>
> The following warnings are thrown very often
> \source-highlight-3.1\lib\srchilite\fileutil.h(28) : warning C4290: C++
> exception specification ignored except to indicate a function is not
> __declspec(nothrow)
> \source-highlight-3.1\lib\srchilite\formatterparams.h(18) : warning
> C4099: 'srchilite::FormatterParams' : type name first seen using 'class'
> now seen using 'struct'
> \source-highlight-3.1\lib\srchilite\sourcehighlighter.h(22) : see
> declaration of 'srchilite::FormatterParams'
> \source-highlight-3.1\lib\srchilite\eventgenerator.h(31) : warning
> C4800: 'unsigned int' : forcing value to bool 'true' or 'false'
> (performance warning)
>
> Here again config.h does not exist (which really does not exist in the
> libary, nor mingw system header files).
> Is this file generated by autoconf?
> lib\srchilite\settings.cpp(11) : fatal error C1083: Cannot open include
> file: 'config.h': No such file or directory
>
> The following error is much more problematic.
> lib\srchilite\sourcehighlightutils.cpp(15) : fatal error C1083: Cannot
> open include file: 'dirent.h': No such file or directory
>
> This is a header file _only_ existing in gcc derived compilers.
> Wikipedia says about it "The function is not part of the C standard",
> and it is not part of any Visual Studio compiler. This means that if you
> use this header it binds the libary code to gcc.
> I have seen other files where I expect that they only exist in gcc, for
> example <sys/stat.h>, or rather only in unix systems.
>
> lib\srchilite\versions.cpp(18) : error C2065: 'VERSION' : undeclared
> identifier
> lib\srchilite\versions.cpp(22) : error C2065: 'LIBRARY_VERSION' :
> undeclared identifier
> This means that some Preprocessor Variables were not defined, probably
> the same as ABSOLUTEDATADIR in the mingw compilation step.
> Here porting from the old toolchain to the .pro file needs completed,
> but I am missing the necessary information.
>
> You had asked why I want to compile using msvc and did not try your
> mingw compiled binaries.
> Well, it is because I have also projects which currently work only with
> visual studio, and for my new project where this libary
> would be included I do not want to limit myself to either mingw or msvc.
>
> Best Regards,
> Matthias Pospiech
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Help-source-highlight mailing list
> Help-source-highlight@...
> http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: QSource-Highlight 0.2

2009-11-17T14:12:53Z

I just wanted to inform you that I started to provide a qmake build
system both for source-highlight and source-highlight-qt

for source-highlight-qt is basically ready; now I'm working on the
harder one: source-highlight :)

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Compilation failures using qmake + mingw / msvc

2009-11-17T13:37:59Z

I have set up a qmake .pro file to make the libary without autoconf.
(file attached)

You will see in the following issues, that moving away from autoconf and
to windows problems
arise that indicate that the code could be improved in its plattform
independence.
So I do not want to complain that it fails compilation, but want to give
hints to improve the
plattform independence.

Using mingw I run into the following issues:

/source-highlight-3.1/lib/srchilite/settings.cpp:11: config.h: No such
file or directory
/source-highlight-3.1/lib/srchilite/settings.cpp:37: error:
`ABSOLUTEDATADIR' was not declared in this scope
C:/Programme/Qt/SDK/2009.04/mingw/bin/../lib/gcc/mingw32/3.4.5/../../../../include/io.h:176:
error: too many arguments to function `int mkdir(const char*)'
/source-highlight-3.1/lib/srchilite/settings.cpp:90: error: at this
point in file

so that complition is stopped at settings.cpp.

Compling with msvc-2005 is more problematic:

The following warnings are thrown very often
\source-highlight-3.1\lib\srchilite\fileutil.h(28) : warning C4290: C++
exception specification ignored except to indicate a function is not
__declspec(nothrow)
\source-highlight-3.1\lib\srchilite\formatterparams.h(18) : warning
C4099: 'srchilite::FormatterParams' : type name first seen using 'class'
now seen using 'struct'
\source-highlight-3.1\lib\srchilite\sourcehighlighter.h(22) : see
declaration of 'srchilite::FormatterParams'
\source-highlight-3.1\lib\srchilite\eventgenerator.h(31) : warning
C4800: 'unsigned int' : forcing value to bool 'true' or 'false'
(performance warning)

Here again config.h does not exist (which really does not exist in the
libary, nor mingw system header files).
Is this file generated by autoconf?
lib\srchilite\settings.cpp(11) : fatal error C1083: Cannot open include
file: 'config.h': No such file or directory

The following error is much more problematic.
lib\srchilite\sourcehighlightutils.cpp(15) : fatal error C1083: Cannot
open include file: 'dirent.h': No such file or directory

This is a header file _only_ existing in gcc derived compilers.
Wikipedia says about it "The function is not part of the C standard",
and it is not part of any Visual Studio compiler. This means that if you
use this header it binds the libary code to gcc.
I have seen other files where I expect that they only exist in gcc, for
example <sys/stat.h>, or rather only in unix systems.

lib\srchilite\versions.cpp(18) : error C2065: 'VERSION' : undeclared
identifier
lib\srchilite\versions.cpp(22) : error C2065: 'LIBRARY_VERSION' :
undeclared identifier
This means that some Preprocessor Variables were not defined, probably
the same as ABSOLUTEDATADIR in the mingw compilation step.
Here porting from the old toolchain to the .pro file needs completed,
but I am missing the necessary information.

You had asked why I want to compile using msvc and did not try your
mingw compiled binaries.
Well, it is because I have also projects which currently work only with
visual studio, and for my new project where this libary
would be included I do not want to limit myself to either mingw or msvc.

Best Regards,
Matthias Pospiech

CONFIG += release
CONFIG -= debug
CONFIG -= qt
CONFIG += thread warn_on

TEMPLATE = lib
CONFIG += dll
# CONFIG += staticlib

TARGET = source-highlight

# -------------------------------------------------
# Define Variables
# -------------------------------------------------
BINARY_NAME = TARGET
BUILD_DIR = build
BIN_DIR = bin

# -------------------------------------------------
# Auto select compiler
# -------------------------------------------------
win32-g++: COMPILER = mingw
win32-msvc2005: COMPILER = msvc-2005
linux-g++: COMPILER = gcc

message(Compiler Binary: $$QMAKE_CXX)
message(Compiler Path: $${COMPILER})

# -------------------------------------------------
win32 {
RELEASE_SUFFIX =
DEBUG_SUFFIX = d
}

CONFIG(debug, debug|release) {
SUFFIX_STR = $${DEBUG_SUFFIX}
}
else {
SUFFIX_STR = $${RELEASE_SUFFIX}
}

# -------------------------------------------------
# Target Directory
# -------------------------------------------------
debug:DESTDIR = $${BIN_DIR}/$${COMPILER}/debug/
release:DESTDIR = $${BIN_DIR}/$${COMPILER}/release/

# -------------------------------------------------
# Executable Filename
# -------------------------------------------------
TARGET = $${BINARY_NAME}$${SUFFIX_STR}

# -------------------------------------------------
# Prepocessor Definitions
# -------------------------------------------------
win32{
DEFINES += WIN32
DEFINES += _WINDOWS
debug {
DEFINES += _DEBUG
}
release {
DEFINES += NDEBUG
}
}
DEFINES += NOMINMAX
DEFINES += BOOST_REGEX_DYN_LINK
DEFINES += _CRT_SECURE_NO_WARNINGS
# -------------------------------------------------
# Objects Directory
# -------------------------------------------------
debug{
OBJECTS_DIR = $${BUILD_DIR}/$${BINARY_NAME}/debug/
}
release{
OBJECTS_DIR = $${BUILD_DIR}/$${BINARY_NAME}/release/
}

# -------------------------------------------------
# Moc Directory
# -------------------------------------------------
MOC_DIR = $${BUILD_DIR}/$${BINARY_NAME}/

# -------------------------------------------------
# Ui Directory
# -------------------------------------------------
UI_DIR = $${BUILD_DIR}/$${BINARY_NAME}/ui

# -------------------------------------------------
# Include directories
# -------------------------------------------------
INCLUDEPATH += lib/srchilite \
../boost_1_40_0

# -------------------------------------------------
# Libaries
# -------------------------------------------------

contains($${COMPILER}, msvc-2005) {
# dll
# debug: LIBS += -Llib/boost/regex/$${COMPILER}/debug -lboost_regex-vc80-mt-gd-1_40
# release:LIBS += -Llib/boost/regex/$${COMPILER}/release -lboost_regex-vc80-mt-1_40
# static
debug: LIBS += -Llib/boost/regex/$${COMPILER}/debug -llibboost_regex-vc80-mt-gd-1_40
release:LIBS += -Llib/boost/regex/$${COMPILER}/release -llibboost_regex-vc80-mt-1_40
}

contains($${COMPILER}, mingw) {
debug: LIBS += -Llib/boost/regex/$${COMPILER}/debug -lboost_regex-mgw34-mt-d-1_40
release:LIBS += -Llib/boost/regex/$${COMPILER}/release -lboost_regex-mgw34-mt-1_40
}

# -------------------------------------------------
# Sources
# -------------------------------------------------

SOURCES += lib/srchilite/bufferedoutput.cpp \
lib/srchilite/ctagscollector.cpp \
lib/srchilite/ctagsformatter.cpp \
lib/srchilite/ctagsmanager.cpp \
lib/srchilite/debuglistener.cpp \
lib/srchilite/delimitedlangelem.cpp \
lib/srchilite/doctemplate.cpp \
lib/srchilite/fileinfo.cpp \
lib/srchilite/formatter.cpp \
lib/srchilite/formattermanager.cpp \
lib/srchilite/highlightbuilderexception.cpp \
lib/srchilite/highlightrule.cpp \
lib/srchilite/highlightrulefactory.cpp \
lib/srchilite/highlightstate.cpp \
lib/srchilite/highlightstatebuilder.cpp \
lib/srchilite/highlightstateprinter.cpp \
lib/srchilite/highlighttoken.cpp \
lib/srchilite/ioexception.cpp \
lib/srchilite/langdefmanager.cpp \
lib/srchilite/langelem.cpp \
lib/srchilite/langelems.cpp \
lib/srchilite/langelemsprinter.cpp \
lib/srchilite/langmap.cpp \
lib/srchilite/languageinfer.cpp \
lib/srchilite/linenumgenerator.cpp \
lib/srchilite/lineranges.cpp \
lib/srchilite/namedsubexpslangelem.cpp \
lib/srchilite/parserexception.cpp \
lib/srchilite/preformatter.cpp \
lib/srchilite/regexhighlightrule.cpp \
lib/srchilite/regexpreprocessor.cpp \
lib/srchilite/regexranges.cpp \
lib/srchilite/regexrulefactory.cpp \
lib/srchilite/settings.cpp \
lib/srchilite/sourcefilehighlighter.cpp \
lib/srchilite/sourcehighlight.cpp \
lib/srchilite/sourcehighlighter.cpp \
lib/srchilite/sourcehighlightutils.cpp \
lib/srchilite/srcuntabifier.cpp \
lib/srchilite/statelangelem.cpp \
lib/srchilite/statestartlangelem.cpp \
lib/srchilite/stopwatch.cpp \
lib/srchilite/stringdef.cpp \
lib/srchilite/stringlistlangelem.cpp \
lib/srchilite/stringtable.cpp \
lib/srchilite/stylefileparser.cpp \
lib/srchilite/substfun.cpp \
lib/srchilite/test_readtags_main.cpp \
lib/srchilite/textstyle.cpp \
lib/srchilite/textstylebuilder.cpp \
lib/srchilite/textstyleformatter.cpp \
lib/srchilite/textstyleformatterfactory.cpp \
lib/srchilite/utils.cpp \
lib/srchilite/vardefinitions.cpp \
lib/srchilite/verbosity.cpp \
lib/srchilite/versions.cpp \
lib/srchilite/wordtokenizer.cpp

HEADERS += bufferedoutput.h \
chartranslator.h \
colormap.h \
colors.h \
copyright.h \
ctagscollector.h \
ctagsformatter.h \
ctagsmanager.h \
debuglistener.h \
delimitedlangelem.h \
docgenerator.h \
doctemplate.h \
eventgenerator.h \
fileinfo.h \
fileutil.h \
formatter.h \
formatterfactory.h \
formattermanager.h \
formatterparams.h \
highlightbuilderexception.h \
highlightevent.h \
highlighteventlistener.h \
highlightrule.h \
highlightrulefactory.h \
highlightstate.h \
highlightstatebuilder.h \
highlightstateprinter.h \
highlighttoken.h \
instances.h \
ioexception.h \
keys.h \
langdefmanager.h \
langdefparser.h \
langdefparserfun.h \
langdefscanner.h \
langelem.h \
langelems.h \
langelemsprinter.h \
langmap.h \
languageinfer.h \
linebuffer.h \
linenumgenerator.h \
lineranges.h \
matchingparameters.h \
namedsubexpslangelem.h \
outlangdefparser.h \
outlangdefparserfun.h \
outlangdefscanner.h \
parserexception.h \
parserinfo.h \
parsestruct.h \
parsestyles.h \
preformatter.h \
readtags.h \
refposition.h \
regexhighlightrule.h \
regexpreprocessor.h \
regexranges.h \
regexrulefactory.h \
reportbugs.h \
settings.h \
sourcefilehighlighter.h \
sourcehighlight.h \
sourcehighlighter.h \
sourcehighlightutils.h \
srcuntabifier.h \
statelangelem.h \
statestartlangelem.h \
stopwatch.h \
stringdef.h \
stringlistlangelem.h \
stringtable.h \
stylecssparser.h \
stylefileparser.h \
stylekey.h \
styleparser.h \
substfun.h \
textstyle.h \
textstylebuilder.h \
textstyleformatter.h \
textstyleformattercollection.h \
textstyleformatterfactory.h \
textstyles.h \
tostringcollection.h \
utils.h \
vardefinitions.h \
verbosity.h \
versions.h \
wordtokenizer.h

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: QSource-Highlight 0.2

2009-11-17T06:03:46Z

Matthias Pospiech wrote:

> Lorenzo Bettini schrieb:
>> Matthias Pospiech wrote:
>>> Lorenzo Bettini schrieb:
>>>>
>>>>
>>>> actually they're both platform independent; it's true that they rely
>>>> on a unix-like system for building, but in windows you have both
>>>> cygwin and mingw/msys for that. Indeed there's a windows build of
>>>> source-highlight that I did with mingw:
>>>> http://www.lorenzobettini.it/software/source-highlight/
>>>>
>>> Actually I want to build it on my own. I need a mingw build
>>> compatible with the mingw Version of Qt 4.5 and a Visual Studio build
>>> for Version 2005, 2008 and soon 2010.
>>>
>>> So what I really need is a solution to build the libary on windows on
>>> my own.
>>> What I do not understand in the first place is how I run the
>>> configure script without sh.
>>>
>>
>> Hi Matthias
>>
>> if you want to build it yourself then you also need a shell to run
>> configure, and if you use mingw you'd need msys (which provides a
>> shell and other tools); but to build source-highlight you also need
>> the boost library for mingw.
>>
>> Thus, if you haven't already setup such an environment mingw/msys it
>> might take some time.
>>
> I was trying to set up a system with msys, but did not have success so
> far. However what bothers me most is the compilation with msvc.
> The only build step I could find is this one:
> http://folti.blogs.balabit.com/2009/08/compiling-autoconfmake-using-sources.html
>
> which is really a way to fight around all problems of autoconf on
> non.unix platform issues and not a clean solution.
>
> I wonder how difficult building of source-highlight really is. I think
> putting all cpp+h files in a qmake project costs me only a few minutes.
> Only the boost libary might be a problem since it does not build as a
> shared libary on mingw.

Hi Matthias

probably I missed something: do you use mingw or msvc? As for msvc I
cannot tell, since I basically don't use those build tools.

As for boost, why do you actually need a dll? can't you just use a
static build of boost, like the one I inserted in the archive?

Have you tried to use the binary archive I told you about yesterday?
http://gdn.dsi.unifi.it/~bettini/binaries/source-highlight-qt-win32-0.2.tar.gz

If you need a version which is compatible with mingw and qt, then this
version should do, since those are the tools I've built them with.

As for using qmake for source-highlight (and most importantly
source-highlight-qt) it's a good idea. Note that I'm not willing to
abandon autotools, but I think I can also provide the .pro files to be
able to build them with qmake. Note that in that case it would only be
a build of the library and binary and not of the documentation and
related stuff.

hope to hear from you soon

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: QSource-Highlight 0.2

2009-11-17T05:13:44Z

Lorenzo Bettini schrieb:

> Matthias Pospiech wrote:
>> Lorenzo Bettini schrieb:
>>>
>>>
>>> actually they're both platform independent; it's true that they rely
>>> on a unix-like system for building, but in windows you have both
>>> cygwin and mingw/msys for that. Indeed there's a windows build of
>>> source-highlight that I did with mingw:
>>> http://www.lorenzobettini.it/software/source-highlight/
>>>
>> Actually I want to build it on my own. I need a mingw build
>> compatible with the mingw Version of Qt 4.5 and a Visual Studio build
>> for Version 2005, 2008 and soon 2010.
>>
>> So what I really need is a solution to build the libary on windows on
>> my own.
>> What I do not understand in the first place is how I run the
>> configure script without sh.
>>
>
> Hi Matthias
>
> if you want to build it yourself then you also need a shell to run
> configure, and if you use mingw you'd need msys (which provides a
> shell and other tools); but to build source-highlight you also need
> the boost library for mingw.
>
> Thus, if you haven't already setup such an environment mingw/msys it
> might take some time.
>

I was trying to set up a system with msys, but did not have success so
far. However what bothers me most is the compilation with msvc.
The only build step I could find is this one:
http://folti.blogs.balabit.com/2009/08/compiling-autoconfmake-using-sources.html
which is really a way to fight around all problems of autoconf on
non.unix platform issues and not a clean solution.

I wonder how difficult building of source-highlight really is. I think
putting all cpp+h files in a qmake project costs me only a few minutes.
Only the boost libary might be a problem since it does not build as a
shared libary on mingw.

Matthias

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: QSource-Highlight 0.2

2009-11-16T14:22:31Z

Matthias Pospiech wrote:

> Lorenzo Bettini schrieb:
>>
>>
>> actually they're both platform independent; it's true that they rely
>> on a unix-like system for building, but in windows you have both
>> cygwin and mingw/msys for that. Indeed there's a windows build of
>> source-highlight that I did with mingw:
>> http://www.lorenzobettini.it/software/source-highlight/
>>
> Actually I want to build it on my own. I need a mingw build compatible
> with the mingw Version of Qt 4.5 and a Visual Studio build for Version
> 2005, 2008 and soon 2010.
>
> So what I really need is a solution to build the libary on windows on my
> own.
> What I do not understand in the first place is how I run the configure
> script without sh.
>

Hi Matthias

if you want to build it yourself then you also need a shell to run
configure, and if you use mingw you'd need msys (which provides a shell
and other tools); but to build source-highlight you also need the boost
library for mingw.

Thus, if you haven't already setup such an environment mingw/msys it
might take some time.

For this reason, I've just put up a binary distribution which includes
source-highlight-qt library, boost regex library, and source-highlight
(and its library) for window; if you feel like trying it you can
download it from here
http://gdn.dsi.unifi.it/~bettini/binaries/source-highlight-qt-win32-0.2.tar.gz
(it's more than 6 mega of course); using this, I've also built the
qeditexample (the example that uses source-highlight-qt, downloadable in
source format from here
http://sourceforge.net/projects/srchiliteqt/files/), e.g., here's the
built binary:
http://gdn.dsi.unifi.it/~bettini/binaries/qeditexample-win32-1.1.zip.

Of course, you still need the qt 4.5 dll libraries; in particular I've
used the latest 4.5 qt distribution for windows (which also offers to
download, during its installation, a minimal mingw compiler and
corresponding .dll which is needed as well).

Note that once you have the above binary package of source-highlight-qt,
then you can do everything with qmake; indeed qeditexample simply relies
on qmake. Once I installed the above binary version (i.e., extracted
the zip on C:, everything will be extracted into c:\usr\local...), I
opened the Qt command prompt, and ran

qmake -recursive LIBS+="-L\usr\local\lib -lsource-highlight-qt4
-lsource-highlight -lboost_regex-mt" INCPATH+="\usr\local\include"
qeditexample.pro

and then

mingw32-make

Note that qmake might complain since it cannot find pkg-config, the tool
it will try to use to find source-highlight-qt library, but you can
ignore it, since you provided it with LIBS and INCPATH.

Thus, if your build environment relies on qmake, you only need the above
binary package (and you don't need to bother getting a unix shell like
msys).

Using the same technique I'll build a windows version of
qsource-highlight; in this case, since it's an application, I can add to
the zip also the required qt and mingw dlls; instead in the case of
source-highlight-qt, being a library intended to be used with qt, it's
safe to assume that the user already has qt (and mingw) installed.

Please, do not hesitate to write for any further help; I'm pretty
interested in making the use of source-highlight-qt under windows as well.

hope to hear from you soon
cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: QSource-Highlight 0.2

2009-11-16T12:57:01Z

Lorenzo Bettini schrieb:
>
>
> actually they're both platform independent; it's true that they rely
> on a unix-like system for building, but in windows you have both
> cygwin and mingw/msys for that. Indeed there's a windows build of
> source-highlight that I did with mingw:
> http://www.lorenzobettini.it/software/source-highlight/
>
Actually I want to build it on my own. I need a mingw build compatible
with the mingw Version of Qt 4.5 and a Visual Studio build for Version
2005, 2008 and soon 2010.

So what I really need is a solution to build the libary on windows on my
own.
What I do not understand in the first place is how I run the configure
script without sh.

Matthias

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: QSource-Highlight 0.2

2009-11-16T00:25:24Z

Matthias Pospiech wrote:

> Lorenzo Bettini schrieb:
>> Hi
>>
>> I've just released version 0.2 this program:
>>
>> http://qsrchilite.sourceforge.net/
>>
>> QSource-Highlight is a Qt4 front-end for GNU Source-Highlight,
>> http://www.gnu.org/software/src-highlite.
>>
> I downloaded src-highlite and your Qt Wrapper class. But as far as I can
> see neither of them are platform independent.
> Especially src-highlite seems to rely on a unix system for the Makefile
> generation and the INSTALL file of your Wrapper class
> seems to be designed for usage which unix only as well.
>
> If both are really not usable for Windows the whole idea of both
> libaries is useless for me. I develop for windows and port to linux.
> Not the other way!
>
> Best Regards,
> Matthias Pospiech
>

Hi Matthias

actually they're both platform independent; it's true that they rely on
a unix-like system for building, but in windows you have both cygwin and
mingw/msys for that. Indeed there's a windows build of source-highlight
that I did with mingw:
http://www.lorenzobettini.it/software/source-highlight/

if you need a windows build for source-highlight-qt I can do that.

I'm using source-highlight and source-highlight-qt on windows myself for
qsource-highlight.

By the way: source-highlight-qt is the library for performing syntax
highlighting in Qt documents; qsource-highlight is a front-end for
source-highlight which relies on source-highlight-qt :)

and for instance, qsource-highlight itself uses qmake for building.

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Re: QSource-Highlight 0.2

2009-11-15T13:52:47Z

Lorenzo Bettini schrieb:
> Hi
>
> I've just released version 0.2 this program:
>
> http://qsrchilite.sourceforge.net/
>
> QSource-Highlight is a Qt4 front-end for GNU Source-Highlight,
> http://www.gnu.org/software/src-highlite.
>
I downloaded src-highlite and your Qt Wrapper class. But as far as I can
see neither of them are platform independent.
Especially src-highlite seems to rely on a unix system for the Makefile
generation and the INSTALL file of your Wrapper class
seems to be designed for usage which unix only as well.

If both are really not usable for Windows the whole idea of both
libaries is useless for me. I develop for windows and port to linux.
Not the other way!

Best Regards,
Matthias Pospiech

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

QSource-Highlight 0.2

2009-11-15T09:38:56Z

Hi

I've just released version 0.2 this program:

http://qsrchilite.sourceforge.net/

QSource-Highlight is a Qt4 front-end for GNU Source-Highlight,
http://www.gnu.org/software/src-highlite.

QSource-Highlight uses the library included in GNU Source-Highlight,
since version 3, thus you need that library to build QSource-Highlight;
in particular it uses Source-Highlight-Qt additional library,
http://srchiliteqt.sourceforge.net, which provides highlighting in Qt
relying on GNU Source-Highlight. Thus, you need to install
Source-Highlight-Qt as well. we refer to GNU Source-Highlight's and
Source-Highlight-Qt's websites for further information about the library
and its installation (you may want to check whether your distribution
already provides packages for these two libraries).

You can highlight your code on the fly, and have the highlighted output
in all the formats supported by source-highlight (e.g., HTML, LaTeX,
Texinfo, etc.). You can then copy the formatted output and paste it
(e.g., in your blog), or save it to a file.

A preview of the highlighted output is available for some output formats
(e.g., HTML, XHTML, etc.).

any feedback is more than welcome :-)

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

QSource-Highlight 0.2

2009-11-15T09:38:56Z

Hi

I've just released version 0.2 this program:

http://qsrchilite.sourceforge.net/

QSource-Highlight is a Qt4 front-end for GNU Source-Highlight,
http://www.gnu.org/software/src-highlite.

QSource-Highlight uses the library included in GNU Source-Highlight,
since version 3, thus you need that library to build QSource-Highlight;
in particular it uses Source-Highlight-Qt additional library,
http://srchiliteqt.sourceforge.net, which provides highlighting in Qt
relying on GNU Source-Highlight. Thus, you need to install
Source-Highlight-Qt as well. we refer to GNU Source-Highlight's and
Source-Highlight-Qt's websites for further information about the library
and its installation (you may want to check whether your distribution
already provides packages for these two libraries).

You can highlight your code on the fly, and have the highlighted output
in all the formats supported by source-highlight (e.g., HTML, LaTeX,
Texinfo, etc.). You can then copy the formatted output and paste it
(e.g., in your blog), or save it to a file.

A preview of the highlighted output is available for some output formats
(e.g., HTML, XHTML, etc.).

any feedback is more than welcome :-)

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Info-source-highlight mailing list
Info-source-highlight@...
http://lists.gnu.org/mailman/listinfo/info-source-highlight

From forum: Gnu - Source Highlight - Announce

QSource-Highlight

2009-10-01T01:04:36Z

Hi

I've just released this program:

http://qsrchilite.sourceforge.net/

QSource-Highlight is a Qt4 front-end for GNU Source-Highlight,
http://www.gnu.org/software/src-highlite.

QSource-Highlight uses the library included in GNU Source-Highlight,
since version 3, thus you need that library to build QSource-Highlight;
in particular it uses Source-Highlight-Qt additional library,
http://srchiliteqt.sourceforge.net, which provides highlighting in Qt
relying on GNU Source-Highlight. Thus, you need to install
Source-Highlight-Qt as well. we refer to GNU Source-Highlight's and
Source-Highlight-Qt's websites for further information about the library
and its installation (you may want to check whether your distribution
already provides packages for these two libraries).

You can highlight your code on the fly, and have the highlighted output
in all the formats supported by source-highlight (e.g., HTML, LaTeX,
Texinfo, etc.). You can then copy the formatted output and paste it
(e.g., in your blog), or save it to a file.

A preview of the highlighted output is available for some output formats
(e.g., HTML, XHTML, etc.).

any feedback is more than welcome :-)

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

QSource-Highlight

2009-10-01T01:04:36Z

Hi

I've just released this program:

http://qsrchilite.sourceforge.net/

QSource-Highlight is a Qt4 front-end for GNU Source-Highlight,
http://www.gnu.org/software/src-highlite.

QSource-Highlight uses the library included in GNU Source-Highlight,
since version 3, thus you need that library to build QSource-Highlight;
in particular it uses Source-Highlight-Qt additional library,
http://srchiliteqt.sourceforge.net, which provides highlighting in Qt
relying on GNU Source-Highlight. Thus, you need to install
Source-Highlight-Qt as well. we refer to GNU Source-Highlight's and
Source-Highlight-Qt's websites for further information about the library
and its installation (you may want to check whether your distribution
already provides packages for these two libraries).

You can highlight your code on the fly, and have the highlighted output
in all the formats supported by source-highlight (e.g., HTML, LaTeX,
Texinfo, etc.). You can then copy the formatted output and paste it
(e.g., in your blog), or save it to a file.

A preview of the highlighted output is available for some output formats
(e.g., HTML, XHTML, etc.).

any feedback is more than welcome :-)

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Info-source-highlight mailing list
Info-source-highlight@...
http://lists.gnu.org/mailman/listinfo/info-source-highlight

From forum: Gnu - Source Highlight - Announce

Source-Highlight-Qt 0.2

2009-09-25T01:55:23Z

Version 0.2 of Source-Highlight-Qt is available at:

http://srchiliteqt.sourceforge.net/

Source-highlight-qt is a library for performing syntax highlighting in
Qt documents by relying on GNU Source-Highlight library,
http://www.gnu.org/software/src-highlite/.

Although the use of GNU Source-highlight library is pretty hidden by
this library, so the programmer must not need the details of GNU
Source-highlight library, yet, some general notions of GNU
Source-highlight might be useful (especially how language definition
files are defined, where the configuration files are stored, etc.).

This library provides an implementation of the qt abstract class
QSyntaxHighlighter class, and it deals both with Qt3 and Qt4, although
you will need to build a separate version of the library for the two
different qt frameworks.
Please note, the Qt3 version has less features and it is there only for
old qt applications; furthermore, QSyntaxHighlighter class in Qt3 has
some design problems which make it quite inefficient to use.

any feedback is more than welcome :-)

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Info-source-highlight mailing list
Info-source-highlight@...
http://lists.gnu.org/mailman/listinfo/info-source-highlight

From forum: Gnu - Source Highlight - Announce

GNU Source-highlight 3.1.1 (with Library)

2009-09-20T15:05:32Z

GNU Source-highlight 3.1.1 has been released. It is available from
ftp://ftp.gnu.org/gnu/src-highlite/ and mirrors of that site (see
list of mirror sites at http://www.gnu.org/order/ftp.html).

GNU Source-highlight, given a source file, produces a document with
syntax highlighting.

Since version 3.0, source-higlight also provides a *C++ highlight
library* that you can use in your programs!

You can also find details about new features of source-highlight on my
blog, in this area:
http://tronprog.blogspot.com/search/label/source-highlight.

At the moment this package can handle

* Ada
* Autoconf files
* C/C++
* C#
* Configuration files (generic)
* Bib
* Bison
* Caml
* Changelog
* Css
* Diff
* Flex
* Fortran
* GLSL
* Haskell (new)
* Haxe
* Html
* ini files
* Java
* Javascript
* KDE desktop files
* Latex
* Ldap files
* Logtalk
* Log files
* lsm files (Linux Software Map)
* Lua
* Makefile
* M4
* ML
* Oz
* Pascal
* Perl
* pkg-config files
* PHP
* Postscript
* Prolog
* Properties files
* Python
* RPM Spec files
* Ruby
* Scala
* Shell
* S-Lang
* Sql
* Tcl
* Texinfo (new)
* XML
* XOrg conf files

as source languages, and

HTML
XHTML
ANSI color escape sequences
LaTeX
Texinfo
DocBook

as output format.

Language definition files and output language definition files, which
are part of source-highlight distribution, can also be downloaded
independently from, respectively:

* http://www.gnu.org/software/src-highlite/lang_files/
* http://www.gnu.org/software/src-highlite/outlang_files/

Source-highlight depends on the Boost regex library
(http://www.boost.org/) so you need to install this library (boost
libraries are usually shipped with most distributions).

Source-highlight can also generate cross references; in order to do this
it relies on GNU Ctags, http://ctags.sourceforge.net.

Version 3.1.1

* access to static global LangDefManager, LangMaps is provided
through the class Instances
* mechanism for setting a global data dir value (e.g., to ensure
consistency in a library) and for checking settings
* library utility functions to retrieve .lang and .outlang files
* fixed default output format to "html.outlang" not "html.lang"
* SourceHighlight class return the output file extension
* the background color for the document is kept empty if it is
not specified in the style file
* SourceHighlight.setLineNumberDigits: to
explicitly set the number of digits for line numbers
* utils.h file is installed in the header directory
* white is a standard color in style files
* language definition file for Texinfo
* language definition file for Haskell (thanks to Sergey Astanin)

Visit the Source-highlight home page at
http://www.gnu.org/software/src-highlite

Anonymous CVS access is also available. Please visit
http://savannah.gnu.org/projects/src-highlite/
where you can find detailed descriptions of how to access the CVS
(read-only). Release-candidate versions are available
through CVS.

Bug reports should go to bug-source-highlight@....

The following mailing lists are available:

* help-source-highlight@..., for generic discussions about the
program and for asking for help about it (open mailing list),
http://mail.gnu.org/mailman/listinfo/help-source-highlight
* info-source-highlight@..., for receiving information about
new releases and features (read-only mailing list),
http://mail.gnu.org/mailman/listinfo/info-source-highlight

if you want to subscribe to a mailing list just go to the URL and follow
the instructions, or send me an e-mail and I'll subscribe you.

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Info-source-highlight mailing list
Info-source-highlight@...
http://lists.gnu.org/mailman/listinfo/info-source-highlight

From forum: Gnu - Source Highlight - Announce

Source-Highlight-Qt

2009-07-06T06:35:05Z

Hi

I've just released this program:

http://srchiliteqt.sourceforge.net/

Source-highlight-qt is a library for performing syntax highlighting in
Qt documents by relying on GNU Source-Highlight library,
http://www.gnu.org/software/src-highlite/.

Although the use of GNU Source-highlight library is pretty hidden by
this library, so the programmer must not need the details of GNU
Source-highlight library, yet, some general notions of GNU
Source-highlight might be useful (especially how language definition
files are defined, where the configuration files are stored, etc.).

This library provides an implementation of the qt abstract class
QSyntaxHighlighter class, and it deals both with Qt3 and Qt4, although
you will need to build a separate version of the library for the two
different qt frameworks.
Please note, the Qt3 version has less features and it is there only for
old qt applications; furthermore, QSyntaxHighlighter class in Qt3 has
some design problems which make it quite inefficient to use.

any feedback is more than welcome :-)

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Help-source-highlight mailing list
Help-source-highlight@...
http://lists.gnu.org/mailman/listinfo/help-source-highlight

From forum: Gnu - Source Highlight - Help

Source-Highlight-Qt

2009-07-06T06:34:13Z

Hi

I've just released this program:

http://srchiliteqt.sourceforge.net/

Source-highlight-qt is a library for performing syntax highlighting in
Qt documents by relying on GNU Source-Highlight library,
http://www.gnu.org/software/src-highlite/.

Although the use of GNU Source-highlight library is pretty hidden by
this library, so the programmer must not need the details of GNU
Source-highlight library, yet, some general notions of GNU
Source-highlight might be useful (especially how language definition
files are defined, where the configuration files are stored, etc.).

This library provides an implementation of the qt abstract class
QSyntaxHighlighter class, and it deals both with Qt3 and Qt4, although
you will need to build a separate version of the library for the two
different qt frameworks.
Please note, the Qt3 version has less features and it is there only for
old qt applications; furthermore, QSyntaxHighlighter class in Qt3 has
some design problems which make it quite inefficient to use.

any feedback is more than welcome :-)

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Info-source-highlight mailing list
Info-source-highlight@...
http://lists.gnu.org/mailman/listinfo/info-source-highlight

From forum: Gnu - Source Highlight - Announce

GNU Source-highlight 3.1 (with Library)

2009-06-13T07:40:49Z

GNU Source-highlight 3.1 has been released. It is available from
ftp://ftp.gnu.org/gnu/src-highlite/ and mirrors of that site (see
list of mirror sites at http://www.gnu.org/order/ftp.html).

GNU Source-highlight, given a source file, produces a document with
syntax highlighting.

Since version 3.0, source-higlight also provides a *C++ highlight
library* that you can use in your programs!

You can also find details about new features of source-highlight on my
blog, in this area:
http://tronprog.blogspot.com/search/label/source-highlight.

At the moment this package can handle

* Ada
* Autoconf files
* C/C++
* C#
* Configuration files (generic)
* Bib
* Bison
* Caml
* Changelog
* Css
* Diff
* Flex
* Fortran
* GLSL
* Haxe
* Html
* ini files
* Java
* Javascript
* KDE desktop files
* Latex
* Ldap files
* Logtalk
* Log files
* lsm files (Linux Software Map)
* Lua
* Makefile
* M4
* ML
* Oz (new)
* Pascal
* Perl
* pkg-config files
* PHP
* Postscript
* Prolog
* Properties files
* Python
* RPM Spec files
* Ruby
* Scala
* Shell
* S-Lang
* Sql
* Tcl
* XML
* XOrg conf files

as source languages, and

HTML
XHTML
ANSI color escape sequences
LaTeX
Texinfo
DocBook

as output format.

Language definition files and output language definition files, which
are part of source-highlight distribution, can also be downloaded
independently from, respectively:

* http://www.gnu.org/software/src-highlite/lang_files/
* http://www.gnu.org/software/src-highlite/outlang_files/

Source-highlight depends on the Boost regex library
(http://www.boost.org/) so you need to install this library (boost
libraries are usually shipped with most distributions).

Source-highlight can also generate cross references; in order to do this
it relies on GNU Ctags, http://ctags.sourceforge.net.

Version 3.1

* library utility functions to retrieve .style and .css files
* fixed library manual link in index.html
* doxyfile is now distributed
* better formatting for < and > in latex output
* doxygen documentation can be built even when building in
a separate directory
* added man page for source-highlight-settings
* language definition for Oz, thanks to David Bremners

Visit the Source-highlight home page at
http://www.gnu.org/software/src-highlite

Anonymous CVS access is also available. Please visit
http://savannah.gnu.org/projects/src-highlite/
where you can find detailed descriptions of how to access the CVS
(read-only). Release-candidate versions are available
through CVS.

Bug reports should go to bug-source-highlight@....

The following mailing lists are available:

* help-source-highlight@..., for generic discussions about the
program and for asking for help about it (open mailing list),
http://mail.gnu.org/mailman/listinfo/help-source-highlight
* info-source-highlight@..., for receiving information about
new releases and features (read-only mailing list),
http://mail.gnu.org/mailman/listinfo/info-source-highlight

if you want to subscribe to a mailing list just go to the URL and follow
the instructions, or send me an e-mail and I'll subscribe you.

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Info-source-highlight mailing list
Info-source-highlight@...
http://lists.gnu.org/mailman/listinfo/info-source-highlight

From forum: Gnu - Source Highlight - Announce

GNU Source-highlight 3.0 (with Library)

2009-05-10T06:50:25Z

GNU Source-highlight 3.0 has been released. It is available from
ftp://ftp.gnu.org/gnu/src-highlite/ and mirrors of that site (see
list of mirror sites at http://www.gnu.org/order/ftp.html).

GNU Source-highlight, given a source file, produces a document with
syntax highlighting.

Since version 3.0, source-higlight also provides a *C++ highlight
library* that you can use in your programs!

You can also find details about new features of source-highlight on my
blog, in this area:
http://tronprog.blogspot.com/search/label/source-highlight.

At the moment this package can handle

* Ada
* Autoconf files
* C/C++
* C#
* Configuration files (generic) (new)
* Bib
* Bison
* Caml
* Changelog
* Css
* Diff
* Flex
* Fortran
* GLSL
* Haxe
* Html
* ini files
* Java
* Javascript
* KDE desktop files
* Latex
* Ldap files
* Logtalk
* Log files
* lsm files (Linux Software Map)
* Lua
* Makefile
* M4
* ML
* Pascal
* Perl
* pkg-config files (new)
* PHP
* Postscript
* Prolog
* Properties files
* Python
* RPM Spec files
* Ruby
* Scala
* Shell
* S-Lang
* Sql
* Tcl
* XML
* XOrg conf files

as source languages, and

HTML
XHTML
ANSI color escape sequences
LaTeX
Texinfo
DocBook

as output format.

Language definition files and output language definition files, which
are part of source-highlight distribution, can also be downloaded
independently from, respectively:

* http://www.gnu.org/software/src-highlite/lang_files/
* http://www.gnu.org/software/src-highlite/outlang_files/

Source-highlight depends on the Boost regex library
(http://www.boost.org/) so you need to install this library (boost
libraries are usually shipped with most distributions).

Source-highlight can also generate cross references; in order to do this
it relies on GNU Ctags, http://ctags.sourceforge.net.

Version 3.0

* provides a library for highlighting that can be used
by other programs.
* --regex-range (highlight only specified lines of an input file,
according to specific regular expressions describing the delimiting
lines).
* deal with HTML5 features (thanks to Simon Pieters)
* use --docdir for documentation directory
* --binary-output command line option to write output files in binary
mode
* Added the program source-highlight-settings to write a configuration
file for source-highlight (and its library) in the user home
directory.
* languange definition for generic configuration files
* languange definition for pkg-config files
* the input language is now discovered also using the whole file
name (besides the file extension if any)
* in .lang files one can specify the exit level

Visit the Source-highlight home page at
http://www.gnu.org/software/src-highlite

Anonymous CVS access is also available. Please visit
http://savannah.gnu.org/projects/src-highlite/
where you can find detailed descriptions of how to access the CVS
(read-only). Release-candidate versions are available
through CVS.

Bug reports should go to bug-source-highlight@....

The following mailing lists are available:

* help-source-highlight@..., for generic discussions about the
program and for asking for help about it (open mailing list),
http://mail.gnu.org/mailman/listinfo/help-source-highlight
* info-source-highlight@..., for receiving information about
new releases and features (read-only mailing list),
http://mail.gnu.org/mailman/listinfo/info-source-highlight

if you want to subscribe to a mailing list just go to the URL and follow
the instructions, or send me an e-mail and I'll subscribe you.

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Info-source-highlight mailing list
Info-source-highlight@...
http://lists.gnu.org/mailman/listinfo/info-source-highlight

From forum: Gnu - Source Highlight - Announce