Re: GTK/Gnome frontend elementary support
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | It would be a good idea to grab what Alejandro did last year. He made | these abstract tool/menubar from the old devel branch for gnome. We should probably have a "stub" frontend that contains all Files/class that is absolutely needed for all frontends. Lgb
Re: GTK/Gnome frontend elementary support
On 26 Jul 2000, Jean-Marc Lasgouttes wrote: "Juergen" == Juergen Vigna [EMAIL PROTECTED] writes: Juergen BTW.: This now is in cvs and working it seems, now Marko has Juergen just to provide the Menubar and Toolbar pimpl files Juergen (otherwise they have to be linked in from the xforms Juergen directory)! It would be a good idea to grab what Alejandro did last year. He made these abstract tool/menubar from the old devel branch for gnome. I would like to look on the code, but for some unknown reason I can't reach Mexican mirror of LyX site : http://www.mx.lyx.org/glyx/ . Maybe I need a visa? Anyway, can someone send me the code developed for gLyX? Marko
Re: GTK/Gnome frontend elementary support
On Thu, 27 Jul 2000, Marko Vendelin wrote: I would like to look on the code, but for some unknown reason I can't reach Mexican mirror of LyX site : http://www.mx.lyx.org/glyx/ . Maybe I need a visa? Anyway, can someone send me the code developed for gLyX? The machine where the mirror was hosted was unplugged from the net because several problems it got. I'll move all the stuff to another machine today. Greets, Alejandro
Re: GTK/Gnome frontend elementary support
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | It would be a good idea to grab what Alejandro did last year. He made | these abstract tool/menubar from the old devel branch for gnome. We should probably have a "stub" frontend that contains all Files/class that is absolutely needed for all frontends. Lgb
Re: GTK/Gnome frontend elementary support
On 26 Jul 2000, Jean-Marc Lasgouttes wrote: > > "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes: > > Juergen> BTW.: This now is in cvs and working it seems, now Marko has > Juergen> just to provide the Menubar and Toolbar pimpl files > Juergen> (otherwise they have to be linked in from the xforms > Juergen> directory)! > > It would be a good idea to grab what Alejandro did last year. He made > these abstract tool/menubar from the old devel branch for gnome. I would like to look on the code, but for some unknown reason I can't reach Mexican mirror of LyX site : http://www.mx.lyx.org/glyx/ . Maybe I need a visa? Anyway, can someone send me the code developed for gLyX? Marko
Re: GTK/Gnome frontend elementary support
On Thu, 27 Jul 2000, Marko Vendelin wrote: > I would like to look on the code, but for some unknown reason I can't > reach Mexican mirror of LyX site : http://www.mx.lyx.org/glyx/ . Maybe I > need a visa? Anyway, can someone send me the code developed for gLyX? The machine where the mirror was hosted was unplugged from the net because several problems it got. I'll move all the stuff to another machine today. Greets, Alejandro
Re: GTK/Gnome frontend elementary support
"Marko" == Marko Vendelin [EMAIL PROTECTED] writes: Marko That's a good point. We can use gtk--/gnome-- only as it is Marko now, but I am not sure whether gnome-- covers libgnome Marko functionality completely. Since all the scripts seems to be Marko working now we may either leave as it is or remove unnecessary Marko scripts. However, if we will need anything directly from gnome Marko libraries we should add these scripts later. Marko Both solutions should work. To check it, I've removed Marko GNOME_INIT, GNOME_COMPILE_WARNINGS, GNOME_X_CHECKS from Marko configure.in file, leaved only config/gnome/gtk--.m4 and Marko config/gnome/gnome--.m4 in autogen.sh script and everything Marko configured/compiled just fine. I think we should try the pure C++ route and remove the rest for now. Therefore, we'll have to think twice before using the C functions directly (or force the foo-- people to improve their support). Could you send a patch? JMarc
Re: GTK/Gnome frontend elementary support
On 26-Jul-2000 Jean-Marc Lasgouttes wrote: I think we should try the pure C++ route and remove the rest for now. Therefore, we'll have to think twice before using the C functions directly (or force the foo-- people to improve their support). Could you send a patch? BTW.: We were discussing about your naming of the src/frontends/gtk directory. Are you planing to do GNOME port or a GTK port? Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450296 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ If at first you do succeed, try to hide your astonishment.
Re: GTK/Gnome frontend elementary support
On Wed, 26 Jul 2000, Juergen Vigna wrote: On 26-Jul-2000 Jean-Marc Lasgouttes wrote: I think we should try the pure C++ route and remove the rest for now. Therefore, we'll have to think twice before using the C functions directly (or force the foo-- people to improve their support). Could you send a patch? The patch is attached. Before committing it I propose to move files gnome--.m4 and gtk--.m4 from config/gnome to config and remove directory config/gnome. BTW.: We were discussing about your naming of the src/frontends/gtk directory. Are you planing to do GNOME port or a GTK port? It seems to me that GNOME port will be easier to accomplish since GNOME libraries have several useful additions comparing with plain GTK. For example, to implement About dialog with GTK I had to write small class with actual implementation. The GNOME has this kind of dialog box already and it is consistent with the similar boxes of other GNOME applications (Gnumeric et al.). I think that this consistency with other GNOME applications is very important and it should make learning and using LyX much easier for new users. I am going on vacation this Friday and, unfortunately, I didn't have any chance to work on LyX recently. To keep the porting to Gnome rolling it might be wise to ask for help from Gnome programmers. However, before announcement in Gnome news site we should be absolutely sure that gnome/gtk frontend builds cleanly and LyX menu/toolbar system is ready for porting. I think that there will be a great interest to this port but it may vanish quickly if LyX is not ready yet. To build LyX as it is now with gtk/gnome frontend enabled one has to 1. add symbolic links that point to ../xforms/Menubar_pimpl.C, ../xforms/Menubar_pimpl.h, ../xforms/Toolbar_pimpl.C, ../xforms/Toolbar_pimpl.h from src/frontend/gtk 2. add these files to Makefile.am file listing (libgtk_la_SOURCES) 3. run configure with the following options: --with-frontend=gtk --without-included-libsigc --disable-sigctest --without-included-string 4. make Marko patch.gnome.cleanup.gz
Re: GTK/Gnome frontend elementary support
It seems to me that GNOME port will be easier to accomplish since GNOME libraries have several useful additions comparing with plain GTK. For example, to implement About dialog with GTK I had to write small class with actual implementation. The GNOME has this kind of dialog box already and it is consistent with the similar boxes of other GNOME applications (Gnumeric et al.). I think that this consistency with other GNOME applications is very important and it should make learning and using LyX much easier for new users. [snip] 1. add symbolic links that point to ../xforms/Menubar_pimpl.C, ../xforms/Menubar_pimpl.h, ../xforms/Toolbar_pimpl.C, ../xforms/Toolbar_pimpl.h from src/frontend/gtk 2. add these files to Makefile.am file listing (libgtk_la_SOURCES) 3. run configure with the following options: --with-frontend=gtk --without-included-libsigc --disable-sigctest --without-included-string Ok then I will put in your patch move the config-files and call the frontend gnome (instead of gtk) also the src/frontends/gtk will be renamed to 'gnome'. Greets Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450296 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Mix's Law: There is nothing more permanent than a temporary building. There is nothing more permanent than a temporary tax.
Re: GTK/Gnome frontend elementary support
Marko Vendelin [EMAIL PROTECTED] writes: | 3. run configure with the following options: |--with-frontend=gtk --without-included-libsigc --disable-sigctest |--without-included-string --without-included-string should not be needed since that will be the default on most systems now. Lgb
Re: GTK/Gnome frontend elementary support
3. run configure with the following options: --with-frontend=gtk --without-included-libsigc --disable-sigctest --without-included-string I thought too that you don't need to add the --without-included-string but if you don't the compilation aborts on lyx_gui.C with some strange error-message from LString.h that someone is included in the wrong order (I lost the whole message on the xterm so I cannot copy it to this mail), but after rerunning configure with --without-included-string compilation went good, now I have to resolve some linking problems..., hmmm, a probably I have to link the Menubar and Toolbar pimpls in, ..., yes now it linked with gnome support enables :) Will commit soon! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450296 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ All work and no pay makes a housewife.
Re: GTK/Gnome frontend elementary support
Juergen Vigna [EMAIL PROTECTED] writes: | | 3. run configure with the following options: | --with-frontend=gtk --without-included-libsigc --disable-sigctest | --without-included-string | | I thought too that you don't need to add the --without-included-string but if | you don't the compilation aborts on lyx_gui.C with some strange error-message | from LString.h that someone is included in the wrong order (I lost the whole | message on the xterm so I cannot copy it to this mail) redo it so that I can fix it. Lgb
Re: GTK/Gnome frontend elementary support
On Wed, 26 Jul 2000, Juergen Vigna wrote: I thought too that you don't need to add the --without-included-string but if you don't the compilation aborts on lyx_gui.C with some strange error-message from LString.h that someone is included in the wrong order (I lost the whole message on the xterm so I cannot copy it to this mail), but after rerunning configure with --without-included-string compilation went good, ... On my system (redhat-6.1, gcc 2.95.2) I don't have this problem. "--with-frontend=gtk --without-included-libsigc --disable-sigctest " works fine here. Marko
Re: GTK/Gnome frontend elementary support
On 26-Jul-2000 Marko Vendelin wrote: On my system (redhat-6.1, gcc 2.95.2) I don't have this problem. "--with-frontend=gtk --without-included-libsigc --disable-sigctest " works fine here. Here too I don't know what it was before, probably a missing make maintainer-clean now I retried and it worked, so Lars all ok on your side! BTW.: This now is in cvs and working it seems, now Marko has just to provide the Menubar and Toolbar pimpl files (otherwise they have to be linked in from the xforms directory)! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450296 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ "Why must you tell me all your secrets when it's hard enough to love you knowing nothing?" -- Lloyd Cole and the Commotions
Re: GTK/Gnome frontend elementary support
> "Marko" == Marko Vendelin <[EMAIL PROTECTED]> writes: Marko> That's a good point. We can use gtk--/gnome-- only as it is Marko> now, but I am not sure whether gnome-- covers libgnome Marko> functionality completely. Since all the scripts seems to be Marko> working now we may either leave as it is or remove unnecessary Marko> scripts. However, if we will need anything directly from gnome Marko> libraries we should add these scripts later. Marko> Both solutions should work. To check it, I've removed Marko> GNOME_INIT, GNOME_COMPILE_WARNINGS, GNOME_X_CHECKS from Marko> configure.in file, leaved only config/gnome/gtk--.m4 and Marko> config/gnome/gnome--.m4 in autogen.sh script and everything Marko> configured/compiled just fine. I think we should try the pure C++ route and remove the rest for now. Therefore, we'll have to think twice before using the C functions directly (or force the foo-- people to improve their support). Could you send a patch? JMarc
Re: GTK/Gnome frontend elementary support
On 26-Jul-2000 Jean-Marc Lasgouttes wrote: > > I think we should try the pure C++ route and remove the rest for now. > Therefore, we'll have to think twice before using the C functions > directly (or force the foo-- people to improve their support). > > Could you send a patch? BTW.: We were discussing about your naming of the src/frontends/gtk directory. Are you planing to do GNOME port or a GTK port? Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450296 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ If at first you do succeed, try to hide your astonishment.
Re: GTK/Gnome frontend elementary support
On Wed, 26 Jul 2000, Juergen Vigna wrote: > On 26-Jul-2000 Jean-Marc Lasgouttes wrote: > > > > I think we should try the pure C++ route and remove the rest for now. > > Therefore, we'll have to think twice before using the C functions > > directly (or force the foo-- people to improve their support). > > > > Could you send a patch? The patch is attached. Before committing it I propose to move files gnome--.m4 and gtk--.m4 from config/gnome to config and remove directory config/gnome. > BTW.: We were discussing about your naming of the src/frontends/gtk > directory. Are you planing to do GNOME port or a GTK port? > It seems to me that GNOME port will be easier to accomplish since GNOME libraries have several useful additions comparing with plain GTK. For example, to implement About dialog with GTK I had to write small class with actual implementation. The GNOME has this kind of dialog box already and it is consistent with the similar boxes of other GNOME applications (Gnumeric et al.). I think that this consistency with other GNOME applications is very important and it should make learning and using LyX much easier for new users. I am going on vacation this Friday and, unfortunately, I didn't have any chance to work on LyX recently. To keep the porting to Gnome rolling it might be wise to ask for help from Gnome programmers. However, before announcement in Gnome news site we should be absolutely sure that gnome/gtk frontend builds cleanly and LyX menu/toolbar system is ready for porting. I think that there will be a great interest to this port but it may vanish quickly if LyX is not ready yet. To build LyX as it is now with gtk/gnome frontend enabled one has to 1. add symbolic links that point to ../xforms/Menubar_pimpl.C, ../xforms/Menubar_pimpl.h, ../xforms/Toolbar_pimpl.C, ../xforms/Toolbar_pimpl.h from src/frontend/gtk 2. add these files to Makefile.am file listing (libgtk_la_SOURCES) 3. run configure with the following options: --with-frontend=gtk --without-included-libsigc --disable-sigctest --without-included-string 4. make Marko patch.gnome.cleanup.gz
Re: GTK/Gnome frontend elementary support
> > It seems to me that GNOME port will be easier to accomplish since GNOME > libraries have several useful additions comparing with plain GTK. For > example, to implement About dialog with GTK I had to write small class > with actual implementation. The GNOME has this kind of dialog box already > and it is consistent with the similar boxes of other GNOME applications > (Gnumeric et al.). I think that this consistency with other GNOME > applications is very important and it should make learning and using LyX > much easier for new users. [snip] > > 1. add symbolic links that point to ../xforms/Menubar_pimpl.C, >../xforms/Menubar_pimpl.h, ../xforms/Toolbar_pimpl.C, >../xforms/Toolbar_pimpl.h from src/frontend/gtk > > 2. add these files to Makefile.am file listing (libgtk_la_SOURCES) > > 3. run configure with the following options: >--with-frontend=gtk --without-included-libsigc --disable-sigctest >--without-included-string > Ok then I will put in your patch move the config-files and call the frontend gnome (instead of gtk) also the src/frontends/gtk will be renamed to 'gnome'. Greets Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450296 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Mix's Law: There is nothing more permanent than a temporary building. There is nothing more permanent than a temporary tax.
Re: GTK/Gnome frontend elementary support
Marko Vendelin <[EMAIL PROTECTED]> writes: | 3. run configure with the following options: |--with-frontend=gtk --without-included-libsigc --disable-sigctest |--without-included-string --without-included-string should not be needed since that will be the default on most systems now. Lgb
Re: GTK/Gnome frontend elementary support
> > 3. run configure with the following options: >--with-frontend=gtk --without-included-libsigc --disable-sigctest >--without-included-string I thought too that you don't need to add the --without-included-string but if you don't the compilation aborts on lyx_gui.C with some strange error-message from LString.h that someone is included in the wrong order (I lost the whole message on the xterm so I cannot copy it to this mail), but after rerunning configure with --without-included-string compilation went good, now I have to resolve some linking problems..., hmmm, a probably I have to link the Menubar and Toolbar pimpls in, ..., yes now it linked with gnome support enables :) Will commit soon! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450296 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ All work and no pay makes a housewife.
Re: GTK/Gnome frontend elementary support
Juergen Vigna <[EMAIL PROTECTED]> writes: | > | > 3. run configure with the following options: | >--with-frontend=gtk --without-included-libsigc --disable-sigctest | >--without-included-string | | I thought too that you don't need to add the --without-included-string but if | you don't the compilation aborts on lyx_gui.C with some strange error-message | from LString.h that someone is included in the wrong order (I lost the whole | message on the xterm so I cannot copy it to this mail) redo it so that I can fix it. Lgb
Re: GTK/Gnome frontend elementary support
On Wed, 26 Jul 2000, Juergen Vigna wrote: > I thought too that you don't need to add the --without-included-string but if > you don't the compilation aborts on lyx_gui.C with some strange error-message > from LString.h that someone is included in the wrong order (I lost the whole > message on the xterm so I cannot copy it to this mail), but after rerunning > configure with --without-included-string compilation went good, ... On my system (redhat-6.1, gcc 2.95.2) I don't have this problem. "--with-frontend=gtk --without-included-libsigc --disable-sigctest " works fine here. Marko
Re: GTK/Gnome frontend elementary support
On 26-Jul-2000 Marko Vendelin wrote: > > On my system (redhat-6.1, gcc 2.95.2) I don't have this problem. > "--with-frontend=gtk --without-included-libsigc --disable-sigctest " works > fine here. Here too I don't know what it was before, probably a missing make maintainer-clean now I retried and it worked, so Lars all ok on your side! BTW.: This now is in cvs and working it seems, now Marko has just to provide the Menubar and Toolbar pimpl files (otherwise they have to be linked in from the xforms directory)! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450296 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ "Why must you tell me all your secrets when it's hard enough to love you knowing nothing?" -- Lloyd Cole and the Commotions
Re: GTK/Gnome frontend elementary support
"Marko" == Marko Vendelin [EMAIL PROTECTED] writes: Marko the attached patch together with additional files included into Marko the .tar.gz archive adds elementary support for GTK/Gnome Marko frontend: configure scripts, Gtk/Gnome initialization, Gnome Marko event loop processing, and Copyright dialog box implementation. Marko It should be easy to use this code on the platform with good Marko STL string implementation. In such case you need standard gtk, Marko gnome, libsigc++ , gtk-- and gnome-- libraries. Hello, It seems that we miss an .m4 file which defines AM_PATH_GTK (and probably others). It is now impossible for me to compile for xforms, since the configure file produced by autoconf is plain wrong... Could you send us the files? JMarc
Re: GTK/Gnome frontend elementary support
Hi, It seems that we miss an .m4 file which defines AM_PATH_GTK (and probably others). It is now impossible for me to compile for xforms, since the configure file produced by autoconf is plain wrong... I've obtained a fresh copy of lyx-devel this morning (cvs checkout) and at least xforms frontend works fine here. Current cvs should contain new directories config/gnome src/frontend/gtk Please check, whether you have these directories in your local copy and whether autogen.sh script contains a huge line with "for fil in config/lyxinclude.m4 config/libtool.m4 config/gettext.m4 config/lcmessage.m4 config/progtest.m4 config/sigc++.m4 config/kde.m4 confi g/gnome/aclocal-include.m4 config/gnome/gnome-print-check.m4 ..." Marko
Re: GTK/Gnome frontend elementary support
"Marko" == Marko Vendelin [EMAIL PROTECTED] writes: Marko Please check, whether you have these directories in your local Marko copy and whether autogen.sh script contains a huge line with Marko "for fil in config/lyxinclude.m4 config/libtool.m4 Marko config/gettext.m4 config/lcmessage.m4 config/progtest.m4 Marko config/sigc++.m4 config/kde.m4 confi g/gnome/aclocal-include.m4 Marko config/gnome/gnome-print-check.m4 ..." I do have all this files, but I think you have some gtkxxx.m4 files in your /usr/share/aclocal (or whereever) directory, that got installed when installing gtk. A simple check: grep AM_PATH_GTK config/gnome/*.m4 reveals that this macro is used there, but never defined. JMarc
Re: GTK/Gnome frontend elementary support
I do have all this files, but I think you have some gtkxxx.m4 files in your /usr/share/aclocal (or whereever) directory, that got installed when installing gtk. A simple check: grep AM_PATH_GTK config/gnome/*.m4 reveals that this macro is used there, but never defined. I see! The attached tar.gz and small patch to autogen.sh adds 1 .m4 script (config/gnome/gtk.m4). I've tried to generate configure script with minimal amount of files in /usr/share/aclocal and it worked now in my system. Sorry for the mess. Marko patch.gtk.m4.add.gz config.gnome.tar.gz
Re: GTK/Gnome frontend elementary support
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars | Finally, to make configure script working I had to disable | Lars AC_LANG_CPLUSPLUS in configure.in (line 66). Otherwise gnome Lars configuration | scripts were not working properly. It will be Lars very nice if someone with | good knowledge of configure.in magic Lars would take a look on this | problem. Lars Jean-Marc, can you have a cursory glance at this? I am not sure Lars if we even need the AC_LANG_CPLUSPLUS there. We certinly need the AC_LANG_CPLUSPLUS, since otherwise checks for the C++ compilers features are done with the C compiler :) I put it back in, and added an AC_LANG_CPLUS_PLUS later. In general, configuring with AC_LANG_CPLUS_PLUS would be better, since we will compile with the C++ compiler. If the gnome scripts are broken with C++, they should be fixed. What are the errors? I cannot test, since I do not have gnome installed here. JMarc PS: Marko, are you on the lyx-devel list?
Re: GTK/Gnome frontend elementary support
"Marko" == Marko Vendelin [EMAIL PROTECTED] writes: Marko I see! The attached tar.gz and small patch to autogen.sh adds 1 Marko .m4 script (config/gnome/gtk.m4). I've tried to generate Marko configure script with minimal amount of files in Marko /usr/share/aclocal and it worked now in my system. Sorry for Marko the mess. I have found one in the meantime and can confirm that this work. I will comit soon. JMarc
Re: GTK/Gnome frontend elementary support
We certinly need the AC_LANG_CPLUSPLUS, since otherwise checks for the C++ compilers features are done with the C compiler :) I put it back in, and added an AC_LANG_CPLUS_PLUS later. In general, configuring with AC_LANG_CPLUS_PLUS would be better, since we will compile with the C++ compiler. If the gnome scripts are broken with C++, they should be fixed. What are the errors? I cannot test, since I do not have gnome installed here. Well, it seems that script gtk.m4 fails to compile a small gtk program with AC_LANG_CPLUSPLUS. When I inserted AC_LANG_C before AC_TRY_RUN (gnome/gtk.m4, line 65) and AC_LANG_CPLUSPLUS at the end of this script, the program was compiled. However, the configure script produced slightly different Makefile (one CPPFLAGS option was missing). Thus, to resolve this problem one needs to run AC_TRY_RUN with AC_LANG_C and somehow keep the configuration of AC_LANG_CPLUSPLUS. I don't know how to do it. PS: Marko, are you on the lyx-devel list? yes, almost for an hour already :). Marko
Re: GTK/Gnome frontend elementary support
On 25-Jul-2000 Marko Vendelin wrote: Well, it seems that script gtk.m4 fails to compile a small gtk program with AC_LANG_CPLUSPLUS. When I inserted AC_LANG_C before AC_TRY_RUN Well I guess that gtk is a ONLY C library and so does not compile with a c++ compiler (only a guess but I already had such problems on linking!) Why don't you test only for gtk-- as you need that one? Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450296 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ An intellectual is someone whose mind watches itself. -- Albert Camus
Re: GTK/Gnome frontend elementary support
"Marko" == Marko Vendelin [EMAIL PROTECTED] writes: Marko Well, it seems that script gtk.m4 fails to compile a small gtk Marko program with AC_LANG_CPLUSPLUS. When I inserted AC_LANG_C Marko before AC_TRY_RUN (gnome/gtk.m4, line 65) and AC_LANG_CPLUSPLUS Marko at the end of this script, the program was compiled. However, Marko the configure script produced slightly different Makefile (one Marko CPPFLAGS option was missing). Thus, to resolve this problem one Marko needs to run AC_TRY_RUN with AC_LANG_C and somehow keep the Marko configuration of AC_LANG_CPLUSPLUS. I don't know how to do it. Could you show us this small program? It might be that it uses a valid C syntax that is not valid C++. These things are easy to fix in general. JMarc
Re: GTK/Gnome frontend elementary support
Could you show us this small program? It might be that it uses a valid C syntax that is not valid C++. These things are easy to fix in general. I mean the program used inside the script (gtk.m4) for checking GTK libraries installation. Marko
Re: GTK/Gnome frontend elementary support
"Marko" == Marko Vendelin [EMAIL PROTECTED] writes: Could you show us this small program? It might be that it uses a valid C syntax that is not valid C++. These things are easy to fix in general. Marko I mean the program used inside the script (gtk.m4) for checking Marko GTK libraries installation. Yes, I understand. But which one is it? And what is the error message in config.log? JMarc
Re: GTK/Gnome frontend elementary support
On 25 Jul 2000, Jean-Marc Lasgouttes wrote: Yes, I understand. But which one is it? And what is the error message in config.log? I've checked out the latest version from cvs and everything worked fine! GTK, gnome, gtkmm, gnomemm were configured without any errors. Thus, it is hard for me to reproduce the problem. Marko
Re: GTK/Gnome frontend elementary support
"Marko" == Marko Vendelin [EMAIL PROTECTED] writes: Marko On 25 Jul 2000, Jean-Marc Lasgouttes wrote: Yes, I understand. But which one is it? And what is the error message in config.log? Marko I've checked out the latest version from cvs and everything Marko worked fine! GTK, gnome, gtkmm, gnomemm were configured without Marko any errors. Thus, it is hard for me to reproduce the problem. Yes, you should comment out the AC_LANG_C at line 89 of configure.in. JMarc
Re: GTK/Gnome frontend elementary support
On 25 Jul 2000, Jean-Marc Lasgouttes wrote: Yes, you should comment out the AC_LANG_C at line 89 of configure.in. AC_TRY_RUN compiles gtk program with C++ compiler instead of C compiler. That's why environment variable CFLAGS doesn't have any effect (see line 58, file config/gnome/gtk.m4). If we add line CXXFLAGS="$CXXFLAGS $GTK_CFLAGS" after line 58 then this test is passed. Marko
Re: GTK/Gnome frontend elementary support
On Tue, 25 Jul 2000, Juergen Vigna wrote: Well I guess that gtk is a ONLY C library and so does not compile with a c++ compiler (only a guess but I already had such problems on linking!) Why don't you test only for gtk-- as you need that one? That's a good point. We can use gtk--/gnome-- only as it is now, but I am not sure whether gnome-- covers libgnome functionality completely. Since all the scripts seems to be working now we may either leave as it is or remove unnecessary scripts. However, if we will need anything directly from gnome libraries we should add these scripts later. Both solutions should work. To check it, I've removed GNOME_INIT, GNOME_COMPILE_WARNINGS, GNOME_X_CHECKS from configure.in file, leaved only config/gnome/gtk--.m4 and config/gnome/gnome--.m4 in autogen.sh script and everything configured/compiled just fine. Marko
Re: GTK/Gnome frontend elementary support
> "Marko" == Marko Vendelin <[EMAIL PROTECTED]> writes: Marko> the attached patch together with additional files included into Marko> the .tar.gz archive adds elementary support for GTK/Gnome Marko> frontend: configure scripts, Gtk/Gnome initialization, Gnome Marko> event loop processing, and Copyright dialog box implementation. Marko> It should be easy to use this code on the platform with good Marko> STL string implementation. In such case you need standard gtk, Marko> gnome, libsigc++ , gtk-- and gnome-- libraries. Hello, It seems that we miss an .m4 file which defines AM_PATH_GTK (and probably others). It is now impossible for me to compile for xforms, since the configure file produced by autoconf is plain wrong... Could you send us the files? JMarc
Re: GTK/Gnome frontend elementary support
Hi, > It seems that we miss an .m4 file which defines AM_PATH_GTK (and > probably others). It is now impossible for me to compile for xforms, > since the configure file produced by autoconf is plain wrong... I've obtained a fresh copy of lyx-devel this morning (cvs checkout) and at least xforms frontend works fine here. Current cvs should contain new directories config/gnome src/frontend/gtk Please check, whether you have these directories in your local copy and whether autogen.sh script contains a huge line with "for fil in config/lyxinclude.m4 config/libtool.m4 config/gettext.m4 config/lcmessage.m4 config/progtest.m4 config/sigc++.m4 config/kde.m4 confi g/gnome/aclocal-include.m4 config/gnome/gnome-print-check.m4 ..." Marko
Re: GTK/Gnome frontend elementary support
> "Marko" == Marko Vendelin <[EMAIL PROTECTED]> writes: Marko> Please check, whether you have these directories in your local Marko> copy and whether autogen.sh script contains a huge line with Marko> "for fil in config/lyxinclude.m4 config/libtool.m4 Marko> config/gettext.m4 config/lcmessage.m4 config/progtest.m4 Marko> config/sigc++.m4 config/kde.m4 confi g/gnome/aclocal-include.m4 Marko> config/gnome/gnome-print-check.m4 ..." I do have all this files, but I think you have some gtkxxx.m4 files in your /usr/share/aclocal (or whereever) directory, that got installed when installing gtk. A simple check: grep AM_PATH_GTK config/gnome/*.m4 reveals that this macro is used there, but never defined. JMarc
Re: GTK/Gnome frontend elementary support
> I do have all this files, but I think you have some gtkxxx.m4 files in > your /usr/share/aclocal (or whereever) directory, that got installed > when installing gtk. A simple check: grep AM_PATH_GTK > config/gnome/*.m4 reveals that this macro is used there, but never > defined. I see! The attached tar.gz and small patch to autogen.sh adds 1 .m4 script (config/gnome/gtk.m4). I've tried to generate configure script with minimal amount of files in /usr/share/aclocal and it worked now in my system. Sorry for the mess. Marko patch.gtk.m4.add.gz config.gnome.tar.gz
Re: GTK/Gnome frontend elementary support
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Lars> | Finally, to make configure script working I had to disable | Lars> AC_LANG_CPLUSPLUS in configure.in (line 66). Otherwise gnome Lars> configuration | scripts were not working properly. It will be Lars> very nice if someone with | good knowledge of configure.in magic Lars> would take a look on this | problem. Lars> Jean-Marc, can you have a cursory glance at this? I am not sure Lars> if we even need the AC_LANG_CPLUSPLUS there. We certinly need the AC_LANG_CPLUSPLUS, since otherwise checks for the C++ compilers features are done with the C compiler :) I put it back in, and added an AC_LANG_CPLUS_PLUS later. In general, configuring with AC_LANG_CPLUS_PLUS would be better, since we will compile with the C++ compiler. If the gnome scripts are broken with C++, they should be fixed. What are the errors? I cannot test, since I do not have gnome installed here. JMarc PS: Marko, are you on the lyx-devel list?
Re: GTK/Gnome frontend elementary support
> "Marko" == Marko Vendelin <[EMAIL PROTECTED]> writes: Marko> I see! The attached tar.gz and small patch to autogen.sh adds 1 Marko> .m4 script (config/gnome/gtk.m4). I've tried to generate Marko> configure script with minimal amount of files in Marko> /usr/share/aclocal and it worked now in my system. Sorry for Marko> the mess. I have found one in the meantime and can confirm that this work. I will comit soon. JMarc
Re: GTK/Gnome frontend elementary support
> We certinly need the AC_LANG_CPLUSPLUS, since otherwise checks for the > C++ compilers features are done with the C compiler :) I put it back > in, and added an AC_LANG_CPLUS_PLUS later. > > In general, configuring with AC_LANG_CPLUS_PLUS would be better, since > we will compile with the C++ compiler. If the gnome scripts are broken > with C++, they should be fixed. What are the errors? I cannot test, > since I do not have gnome installed here. Well, it seems that script gtk.m4 fails to compile a small gtk program with AC_LANG_CPLUSPLUS. When I inserted AC_LANG_C before AC_TRY_RUN (gnome/gtk.m4, line 65) and AC_LANG_CPLUSPLUS at the end of this script, the program was compiled. However, the configure script produced slightly different Makefile (one CPPFLAGS option was missing). Thus, to resolve this problem one needs to run AC_TRY_RUN with AC_LANG_C and somehow keep the configuration of AC_LANG_CPLUSPLUS. I don't know how to do it. > PS: Marko, are you on the lyx-devel list? yes, almost for an hour already :). Marko
Re: GTK/Gnome frontend elementary support
On 25-Jul-2000 Marko Vendelin wrote: > > Well, it seems that script gtk.m4 fails to compile a small gtk program > with AC_LANG_CPLUSPLUS. When I inserted AC_LANG_C before AC_TRY_RUN Well I guess that gtk is a ONLY C library and so does not compile with a c++ compiler (only a guess but I already had such problems on linking!) Why don't you test only for gtk-- as you need that one? Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450296 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ An intellectual is someone whose mind watches itself. -- Albert Camus
Re: GTK/Gnome frontend elementary support
> "Marko" == Marko Vendelin <[EMAIL PROTECTED]> writes: Marko> Well, it seems that script gtk.m4 fails to compile a small gtk Marko> program with AC_LANG_CPLUSPLUS. When I inserted AC_LANG_C Marko> before AC_TRY_RUN (gnome/gtk.m4, line 65) and AC_LANG_CPLUSPLUS Marko> at the end of this script, the program was compiled. However, Marko> the configure script produced slightly different Makefile (one Marko> CPPFLAGS option was missing). Thus, to resolve this problem one Marko> needs to run AC_TRY_RUN with AC_LANG_C and somehow keep the Marko> configuration of AC_LANG_CPLUSPLUS. I don't know how to do it. Could you show us this small program? It might be that it uses a valid C syntax that is not valid C++. These things are easy to fix in general. JMarc
Re: GTK/Gnome frontend elementary support
> Could you show us this small program? It might be that it uses a > valid C syntax that is not valid C++. These things are easy to fix in > general. I mean the program used inside the script (gtk.m4) for checking GTK libraries installation. Marko
Re: GTK/Gnome frontend elementary support
> "Marko" == Marko Vendelin <[EMAIL PROTECTED]> writes: >> Could you show us this small program? It might be that it uses a >> valid C syntax that is not valid C++. These things are easy to fix >> in general. Marko> I mean the program used inside the script (gtk.m4) for checking Marko> GTK libraries installation. Yes, I understand. But which one is it? And what is the error message in config.log? JMarc
Re: GTK/Gnome frontend elementary support
On 25 Jul 2000, Jean-Marc Lasgouttes wrote: > Yes, I understand. But which one is it? And what is the error message > in config.log? I've checked out the latest version from cvs and everything worked fine! GTK, gnome, gtkmm, gnomemm were configured without any errors. Thus, it is hard for me to reproduce the problem. Marko
Re: GTK/Gnome frontend elementary support
> "Marko" == Marko Vendelin <[EMAIL PROTECTED]> writes: Marko> On 25 Jul 2000, Jean-Marc Lasgouttes wrote: >> Yes, I understand. But which one is it? And what is the error >> message in config.log? Marko> I've checked out the latest version from cvs and everything Marko> worked fine! GTK, gnome, gtkmm, gnomemm were configured without Marko> any errors. Thus, it is hard for me to reproduce the problem. Yes, you should comment out the AC_LANG_C at line 89 of configure.in. JMarc
Re: GTK/Gnome frontend elementary support
On 25 Jul 2000, Jean-Marc Lasgouttes wrote: > Yes, you should comment out the AC_LANG_C at line 89 of configure.in. AC_TRY_RUN compiles gtk program with C++ compiler instead of C compiler. That's why environment variable CFLAGS doesn't have any effect (see line 58, file config/gnome/gtk.m4). If we add line CXXFLAGS="$CXXFLAGS $GTK_CFLAGS" after line 58 then this test is passed. Marko
Re: GTK/Gnome frontend elementary support
On Tue, 25 Jul 2000, Juergen Vigna wrote: > Well I guess that gtk is a ONLY C library and so does not compile with > a c++ compiler (only a guess but I already had such problems on linking!) > Why don't you test only for gtk-- as you need that one? That's a good point. We can use gtk--/gnome-- only as it is now, but I am not sure whether gnome-- covers libgnome functionality completely. Since all the scripts seems to be working now we may either leave as it is or remove unnecessary scripts. However, if we will need anything directly from gnome libraries we should add these scripts later. Both solutions should work. To check it, I've removed GNOME_INIT, GNOME_COMPILE_WARNINGS, GNOME_X_CHECKS from configure.in file, leaved only config/gnome/gtk--.m4 and config/gnome/gnome--.m4 in autogen.sh script and everything configured/compiled just fine. Marko
Re: GTK/Gnome frontend elementary support
Marko Vendelin [EMAIL PROTECTED] writes: | the attached patch together with additional files included into the | .tar.gz archive adds elementary support for GTK/Gnome frontend: configure | scripts, Gtk/Gnome initialization, Gnome event loop processing, and | Copyright dialog box implementation. Ok, thanks. I have applied the tar file and the patch. | It should be easy to use this code on the platform with good STL string | implementation. In such case you need standard gtk, gnome, libsigc++ , | gtk-- and gnome-- libraries. I have not reducded LyX requirements on the std::string, so that LyX is now able to use the bastring supplied with egcs and gcc 2.95.x. This should make your life a lot easier. I look forward so seeing this work progress further. | Finally, to make configure script working I had to disable | AC_LANG_CPLUSPLUS in configure.in (line 66). Otherwise gnome configuration | scripts were not working properly. It will be very nice if someone with | good knowledge of configure.in magic would take a look on this | problem. Jean-Marc, can you have a cursory glance at this? I am not sure if we even need the AC_LANG_CPLUSPLUS there. Lgb
Re: GTK/Gnome frontend elementary support
Marko Vendelin <[EMAIL PROTECTED]> writes: | the attached patch together with additional files included into the | .tar.gz archive adds elementary support for GTK/Gnome frontend: configure | scripts, Gtk/Gnome initialization, Gnome event loop processing, and | Copyright dialog box implementation. Ok, thanks. I have applied the tar file and the patch. | It should be easy to use this code on the platform with good STL string | implementation. In such case you need standard gtk, gnome, libsigc++ , | gtk-- and gnome-- libraries. I have not reducded LyX requirements on the std::string, so that LyX is now able to use the bastring supplied with egcs and gcc 2.95.x. This should make your life a lot easier. I look forward so seeing this work progress further. | Finally, to make configure script working I had to disable | AC_LANG_CPLUSPLUS in configure.in (line 66). Otherwise gnome configuration | scripts were not working properly. It will be very nice if someone with | good knowledge of configure.in magic would take a look on this | problem. Jean-Marc, can you have a cursory glance at this? I am not sure if we even need the AC_LANG_CPLUSPLUS there. Lgb
Re: GTK/Gnome frontend elementary support
Hello! Wouldn't it be cleaner to fix Lyx , so that lyxstring is used explicitly in Lyx code? Therefore, Lyx will use lyxstring, and Gnome will use string. It is easy to add conversion routines too. For ANSI conforming compilers, lyxstring could be a typedef to string, and conversions just return the string back. This is somewhat the reverse of the current code, where string is typedef to lyxstring. MST Quoting r. Marko Vendelin ([EMAIL PROTECTED]) "GTK/Gnome frontend elementary support": Hi! the attached patch together with additional files included into the .tar.gz archive adds elementary support for GTK/Gnome frontend: configure scripts, Gtk/Gnome initialization, Gnome event loop processing, and Copyright dialog box implementation. It should be easy to use this code on the platform with good STL string implementation. In such case you need standard gtk, gnome, libsigc++ , gtk-- and gnome-- libraries. On my platform (redhat linux 6.1, egcs 1.1.2) LyX uses LyX string class instead of STL string. To use gtk-- and gnome-- with LyX I recompiled these libraries after replacing "#include string" by "#include "LString.h"" in the source files of the libraries. To make our life easier I've written two small scripts that patch gtk-- and gnome-- libraries and compile them. Please note that running these scripts is DANGEROUS since it may change your source files. The following are instructions for getting Gtk/Gnome frontend running in the platforms that lack good STL string implementation (it worked on my platform): * install Gtk, Gnome, and libsigc++ * download gtkmm-1.2.1.tar.gz and gnomemm-1.1.10.tar.gz from http://gtkmm.sourceforge.net/download.html (click "sourceforge download area" on this page) * create a new directory and copy gtkmm-1.2.1.tar.gz, gnomemm-1.1.10.tar.gz, lyxgtk.sh, and str2lyxstr.sh to this directory (lyxgtk.sh and str2lyxstr.sh are attached to this e-mail) * cd to this directory * read and edit script lyxgtk.sh (set source and install directories) * run script lyxgtk.sh * include directory with installed new gtk and gnome libs to PATH and LD_LIBRARY_PATH as first directories (subdirs bin and lib, respectively). * cd to lyx source directory * run autogen.sh * run configure with the following options: --with-frontend=gtk --without-included-libsigc --disable-sigctest --with-gnomemm-config-path=NEW_GNOMEMM_LIB/lib/gnomemmConf.sh --disable-gtkmmtest * run make Please note, that compiled Gtk--/Gnome-- libraries are usable only with LyX. Finally, to make configure script working I had to disable AC_LANG_CPLUSPLUS in configure.in (line 66). Otherwise gnome configuration scripts were not working properly. It will be very nice if someone with good knowledge of configure.in magic would take a look on this problem. Regards, Marko #!/bin/bash # This script is DANGEROUS! It replaces # "#include string" with "#include "LString.h"" in the files in # current directory (recursively!). This can change YOUR source files. # Use it at your own risk. FILELISTCC=`rgrep -r -l "#include string" . | grep "\.cc"` FILELISTH=`rgrep -r -l "#include string" . | grep "\.h"` FILELISTGEN=`rgrep -r -l "#include string" . | grep "\.gen_"` for i in $FILELISTCC $FILELISTH $FILELISTGEN; do cat $i | sed -e 's/#include string/#include "LString.h"/g' .tmpfile mv .tmpfile $i done #!/bin/bash # This script is DANGEROUS! It uses script srt2lyxstr.sh to replace # "#include string" with "#include "LString.h"". This can change YOUR source files. # Use it at your own risk. # extracting GNOME-- and GTK-- tar zxvf gnomemm-1.1.10.tar.gz tar zxvf gtkmm-1.2.1.tar.gz # Please specify the directories with GTK--, GNOME--, LyX source, and the directory # to which new GTK--/GNOME-- libraries should be installed. GTKMMDIR=/home/users/markov/cpp-files/lyx/lyx-gtk/gtkmm-1.2.1 GNOMEMMDIR=/home/users/markov/cpp-files/lyx/lyx-gtk/gnomemm-1.1.10 LIBINSTALLDIR=/home/users/markov/cpp-files/lyx/lyx-gtk/root LYXDIR=/home/users/markov/cpp-files/lyx/lyx-devel # Please note that script creates temporary directory $GTKMMDIR/../.tmpdir . # Change the script if this is not acceptable for you. mkdir $LIBINSTALLDIR export MAKE="make" export CXXFLAGS="-DUSE_INCLUDED_STRING -I$LYXDIR/src" CURRDIR=`pwd` STR2LYXSTR=$CURRDIR/str2lyxstr.sh # gtkmm cd $GTKMMDIR ./configure --prefix=$LIBINSTALLDIR echo -e "all: \ninstall: \n" gdk--/tests/Makefile mv src/gtkmmproc ../.tmpdir $STR2LYXSTR mv ../.tmpdir src/gtkmmproc make make install cd $CURRDIR # gnomemm export PATH=$LIBINSTALLDIR/bin:$PATH cd $GNOMEMMDIR ./configure --prefix=$LIBINSTALLDIR --disabl
Re: GTK/Gnome frontend elementary support
Hello! Wouldn't it be cleaner to fix Lyx , so that lyxstring is used explicitly in Lyx code? Therefore, Lyx will use lyxstring, and Gnome will use string. It is easy to add conversion routines too. For ANSI conforming compilers, lyxstring could be a typedef to string, and conversions just return the string back. This is somewhat the reverse of the current code, where string is typedef to lyxstring. MST Quoting r. Marko Vendelin ([EMAIL PROTECTED]) "GTK/Gnome frontend elementary support": > > Hi! > > the attached patch together with additional files included into the > .tar.gz archive adds elementary support for GTK/Gnome frontend: configure > scripts, Gtk/Gnome initialization, Gnome event loop processing, and > Copyright dialog box implementation. > > It should be easy to use this code on the platform with good STL string > implementation. In such case you need standard gtk, gnome, libsigc++ , > gtk-- and gnome-- libraries. > > On my platform (redhat linux 6.1, egcs 1.1.2) LyX uses LyX string class > instead of STL string. To use gtk-- and gnome-- with LyX I recompiled > these libraries after replacing "#include " by "#include > "LString.h"" in the source files of the libraries. To make our life easier > I've written two small scripts that patch gtk-- and gnome-- libraries and > compile them. Please note that running these scripts is DANGEROUS since it > may change your source files. The following are instructions for getting > Gtk/Gnome frontend running in the platforms that lack good STL string > implementation (it worked on my platform): > > * install Gtk, Gnome, and libsigc++ > > * download gtkmm-1.2.1.tar.gz and gnomemm-1.1.10.tar.gz from > http://gtkmm.sourceforge.net/download.html (click "sourceforge download > area" on this page) > > * create a new directory and copy gtkmm-1.2.1.tar.gz, > gnomemm-1.1.10.tar.gz, lyxgtk.sh, and str2lyxstr.sh > to this directory (lyxgtk.sh and str2lyxstr.sh are attached to this > e-mail) > > * cd to this directory > > * read and edit script lyxgtk.sh (set source and install directories) > > * run script lyxgtk.sh > > * include directory with installed new gtk and gnome libs to PATH and > LD_LIBRARY_PATH as first directories (subdirs bin and lib, > respectively). > > * cd to lyx source directory > > * run autogen.sh > > * run configure with the following options: > --with-frontend=gtk --without-included-libsigc --disable-sigctest > --with-gnomemm-config-path=NEW_GNOMEMM_LIB/lib/gnomemmConf.sh >--disable-gtkmmtest > > * run make > > Please note, that compiled Gtk--/Gnome-- libraries are usable only with > LyX. > > Finally, to make configure script working I had to disable > AC_LANG_CPLUSPLUS in configure.in (line 66). Otherwise gnome configuration > scripts were not working properly. It will be very nice if someone with > good knowledge of configure.in magic would take a look on this problem. > > Regards, > > Marko > #!/bin/bash > > # This script is DANGEROUS! It replaces > # "#include " with "#include "LString.h"" in the files in > # current directory (recursively!). This can change YOUR source files. > # Use it at your own risk. > > FILELISTCC=`rgrep -r -l "#include " . | grep "\.cc"` > FILELISTH=`rgrep -r -l "#include " . | grep "\.h"` > FILELISTGEN=`rgrep -r -l "#include " . | grep "\.gen_"` > > for i in $FILELISTCC $FILELISTH $FILELISTGEN; do > cat $i | sed -e 's/#include /#include "LString.h"/g' > .tmpfile > mv .tmpfile $i > done > #!/bin/bash > > # This script is DANGEROUS! It uses script srt2lyxstr.sh to replace > # "#include " with "#include "LString.h"". This can change YOUR source files. > # Use it at your own risk. > > # extracting GNOME-- and GTK-- > tar zxvf gnomemm-1.1.10.tar.gz > tar zxvf gtkmm-1.2.1.tar.gz > > # Please specify the directories with GTK--, GNOME--, LyX source, and the directory > # to which new GTK--/GNOME-- libraries should be installed. > GTKMMDIR=/home/users/markov/cpp-files/lyx/lyx-gtk/gtkmm-1.2.1 > GNOMEMMDIR=/home/users/markov/cpp-files/lyx/lyx-gtk/gnomemm-1.1.10 > LIBINSTALLDIR=/home/users/markov/cpp-files/lyx/lyx-gtk/root > LYXDIR=/home/users/markov/cpp-files/lyx/lyx-devel > > # Please note that script creates temporary directory $GTKMMDIR/../.tmpdir . > # Change the script if this is not acceptable for you. > > mkdir $LIBINSTALLDIR > > export MAKE="make" > > export CXXFLAGS="-DUSE_INCLUDED_STRING -I$LYXDIR/src" > > CUR
GTK/Gnome frontend elementary support
Hi! the attached patch together with additional files included into the .tar.gz archive adds elementary support for GTK/Gnome frontend: configure scripts, Gtk/Gnome initialization, Gnome event loop processing, and Copyright dialog box implementation. It should be easy to use this code on the platform with good STL string implementation. In such case you need standard gtk, gnome, libsigc++ , gtk-- and gnome-- libraries. On my platform (redhat linux 6.1, egcs 1.1.2) LyX uses LyX string class instead of STL string. To use gtk-- and gnome-- with LyX I recompiled these libraries after replacing "#include string" by "#include "LString.h"" in the source files of the libraries. To make our life easier I've written two small scripts that patch gtk-- and gnome-- libraries and compile them. Please note that running these scripts is DANGEROUS since it may change your source files. The following are instructions for getting Gtk/Gnome frontend running in the platforms that lack good STL string implementation (it worked on my platform): * install Gtk, Gnome, and libsigc++ * download gtkmm-1.2.1.tar.gz and gnomemm-1.1.10.tar.gz from http://gtkmm.sourceforge.net/download.html (click "sourceforge download area" on this page) * create a new directory and copy gtkmm-1.2.1.tar.gz, gnomemm-1.1.10.tar.gz, lyxgtk.sh, and str2lyxstr.sh to this directory (lyxgtk.sh and str2lyxstr.sh are attached to this e-mail) * cd to this directory * read and edit script lyxgtk.sh (set source and install directories) * run script lyxgtk.sh * include directory with installed new gtk and gnome libs to PATH and LD_LIBRARY_PATH as first directories (subdirs bin and lib, respectively). * cd to lyx source directory * run autogen.sh * run configure with the following options: --with-frontend=gtk --without-included-libsigc --disable-sigctest --with-gnomemm-config-path=NEW_GNOMEMM_LIB/lib/gnomemmConf.sh --disable-gtkmmtest * run make Please note, that compiled Gtk--/Gnome-- libraries are usable only with LyX. Finally, to make configure script working I had to disable AC_LANG_CPLUSPLUS in configure.in (line 66). Otherwise gnome configuration scripts were not working properly. It will be very nice if someone with good knowledge of configure.in magic would take a look on this problem. Regards, Marko #!/bin/bash # This script is DANGEROUS! It replaces # "#include string" with "#include "LString.h"" in the files in # current directory (recursively!). This can change YOUR source files. # Use it at your own risk. FILELISTCC=`rgrep -r -l "#include string" . | grep "\.cc"` FILELISTH=`rgrep -r -l "#include string" . | grep "\.h"` FILELISTGEN=`rgrep -r -l "#include string" . | grep "\.gen_"` for i in $FILELISTCC $FILELISTH $FILELISTGEN; do cat $i | sed -e 's/#include string/#include "LString.h"/g' .tmpfile mv .tmpfile $i done #!/bin/bash # This script is DANGEROUS! It uses script srt2lyxstr.sh to replace # "#include string" with "#include "LString.h"". This can change YOUR source files. # Use it at your own risk. # extracting GNOME-- and GTK-- tar zxvf gnomemm-1.1.10.tar.gz tar zxvf gtkmm-1.2.1.tar.gz # Please specify the directories with GTK--, GNOME--, LyX source, and the directory # to which new GTK--/GNOME-- libraries should be installed. GTKMMDIR=/home/users/markov/cpp-files/lyx/lyx-gtk/gtkmm-1.2.1 GNOMEMMDIR=/home/users/markov/cpp-files/lyx/lyx-gtk/gnomemm-1.1.10 LIBINSTALLDIR=/home/users/markov/cpp-files/lyx/lyx-gtk/root LYXDIR=/home/users/markov/cpp-files/lyx/lyx-devel # Please note that script creates temporary directory $GTKMMDIR/../.tmpdir . # Change the script if this is not acceptable for you. mkdir $LIBINSTALLDIR export MAKE="make" export CXXFLAGS="-DUSE_INCLUDED_STRING -I$LYXDIR/src" CURRDIR=`pwd` STR2LYXSTR=$CURRDIR/str2lyxstr.sh # gtkmm cd $GTKMMDIR ./configure --prefix=$LIBINSTALLDIR echo -e "all: \ninstall: \n" gdk--/tests/Makefile mv src/gtkmmproc ../.tmpdir $STR2LYXSTR mv ../.tmpdir src/gtkmmproc make make install cd $CURRDIR # gnomemm export PATH=$LIBINSTALLDIR/bin:$PATH cd $GNOMEMMDIR ./configure --prefix=$LIBINSTALLDIR --disable-gtkmmtest $STR2LYXSTR make make install cp src/gnomemmConf.sh $LIBINSTALLDIR/lib cd $CURRDIR gnome-add.tar.gz gnome-patch.gz
GTK/Gnome frontend elementary support
Hi! the attached patch together with additional files included into the .tar.gz archive adds elementary support for GTK/Gnome frontend: configure scripts, Gtk/Gnome initialization, Gnome event loop processing, and Copyright dialog box implementation. It should be easy to use this code on the platform with good STL string implementation. In such case you need standard gtk, gnome, libsigc++ , gtk-- and gnome-- libraries. On my platform (redhat linux 6.1, egcs 1.1.2) LyX uses LyX string class instead of STL string. To use gtk-- and gnome-- with LyX I recompiled these libraries after replacing "#include " by "#include "LString.h"" in the source files of the libraries. To make our life easier I've written two small scripts that patch gtk-- and gnome-- libraries and compile them. Please note that running these scripts is DANGEROUS since it may change your source files. The following are instructions for getting Gtk/Gnome frontend running in the platforms that lack good STL string implementation (it worked on my platform): * install Gtk, Gnome, and libsigc++ * download gtkmm-1.2.1.tar.gz and gnomemm-1.1.10.tar.gz from http://gtkmm.sourceforge.net/download.html (click "sourceforge download area" on this page) * create a new directory and copy gtkmm-1.2.1.tar.gz, gnomemm-1.1.10.tar.gz, lyxgtk.sh, and str2lyxstr.sh to this directory (lyxgtk.sh and str2lyxstr.sh are attached to this e-mail) * cd to this directory * read and edit script lyxgtk.sh (set source and install directories) * run script lyxgtk.sh * include directory with installed new gtk and gnome libs to PATH and LD_LIBRARY_PATH as first directories (subdirs bin and lib, respectively). * cd to lyx source directory * run autogen.sh * run configure with the following options: --with-frontend=gtk --without-included-libsigc --disable-sigctest --with-gnomemm-config-path=NEW_GNOMEMM_LIB/lib/gnomemmConf.sh --disable-gtkmmtest * run make Please note, that compiled Gtk--/Gnome-- libraries are usable only with LyX. Finally, to make configure script working I had to disable AC_LANG_CPLUSPLUS in configure.in (line 66). Otherwise gnome configuration scripts were not working properly. It will be very nice if someone with good knowledge of configure.in magic would take a look on this problem. Regards, Marko #!/bin/bash # This script is DANGEROUS! It replaces # "#include " with "#include "LString.h"" in the files in # current directory (recursively!). This can change YOUR source files. # Use it at your own risk. FILELISTCC=`rgrep -r -l "#include " . | grep "\.cc"` FILELISTH=`rgrep -r -l "#include " . | grep "\.h"` FILELISTGEN=`rgrep -r -l "#include " . | grep "\.gen_"` for i in $FILELISTCC $FILELISTH $FILELISTGEN; do cat $i | sed -e 's/#include /#include "LString.h"/g' > .tmpfile mv .tmpfile $i done #!/bin/bash # This script is DANGEROUS! It uses script srt2lyxstr.sh to replace # "#include " with "#include "LString.h"". This can change YOUR source files. # Use it at your own risk. # extracting GNOME-- and GTK-- tar zxvf gnomemm-1.1.10.tar.gz tar zxvf gtkmm-1.2.1.tar.gz # Please specify the directories with GTK--, GNOME--, LyX source, and the directory # to which new GTK--/GNOME-- libraries should be installed. GTKMMDIR=/home/users/markov/cpp-files/lyx/lyx-gtk/gtkmm-1.2.1 GNOMEMMDIR=/home/users/markov/cpp-files/lyx/lyx-gtk/gnomemm-1.1.10 LIBINSTALLDIR=/home/users/markov/cpp-files/lyx/lyx-gtk/root LYXDIR=/home/users/markov/cpp-files/lyx/lyx-devel # Please note that script creates temporary directory $GTKMMDIR/../.tmpdir . # Change the script if this is not acceptable for you. mkdir $LIBINSTALLDIR export MAKE="make" export CXXFLAGS="-DUSE_INCLUDED_STRING -I$LYXDIR/src" CURRDIR=`pwd` STR2LYXSTR=$CURRDIR/str2lyxstr.sh # gtkmm cd $GTKMMDIR ./configure --prefix=$LIBINSTALLDIR echo -e "all: \ninstall: \n" > gdk--/tests/Makefile mv src/gtkmmproc ../.tmpdir $STR2LYXSTR mv ../.tmpdir src/gtkmmproc make make install cd $CURRDIR # gnomemm export PATH=$LIBINSTALLDIR/bin:$PATH cd $GNOMEMMDIR ./configure --prefix=$LIBINSTALLDIR --disable-gtkmmtest $STR2LYXSTR make make install cp src/gnomemmConf.sh $LIBINSTALLDIR/lib cd $CURRDIR gnome-add.tar.gz gnome-patch.gz
