Discussion:
[Texmacs-dev] CMake Build System for GNU TeXmacs
Darcy Shen
2018-10-16 11:02:03 UTC
Permalink
I find that Archlinux already use the CMake Build System. However, there must be small problems in it. And it only works fine on GNU/Linux. As for MacOS, I only use the CMake Build System for developing but not packaging.
Massimiliano Gubinelli
2018-10-16 11:48:20 UTC
Permalink
Personally I just use and maintain the TeXmacs.xcodeproj Xcode project in packages/macos. It rely on the standard configure step for set up and just need some minor tweaks afterwards to be able to compile and debug in Xcode.

What do you think are the advantages of a CMake setup?

M
Post by Darcy Shen
I find that Archlinux already use the CMake Build System. However, there must be small problems in it. And it only works fine on GNU/Linux. As for MacOS, I only use the CMake Build System for developing but not packaging.
_______________________________________________
Texmacs-dev mailing list
https://lists.gnu.org/mailman/listinfo/texmacs-dev
Darcy Shen
2018-10-16 15:07:15 UTC
Permalink
Personally, I have no experience with Xcode. I don't know how to build and package GNU TeXmacs on MacOS. Can you document the minor tweaks? And the Qt version we currently use. Normally, I just wait for the official release of GNU TeXmacs. But there is a severe bug in GNU TeXmacs 1.99.8. And this is my fix: https://github.com/texmacs/GNUTeXmacs/commit/fe0b382070e8355426a1356a46bda7b372503cf5 Next Thursday, I will give a talk on GNU TeXmacs for Shanghai Linux User Group. I hope I can distributed my customized TeXmacs.dmg for SHLUG guys to try. And in my opinion, CMake is better and easier to maintain than our long `configure` file. And I have introduced gtest in CMake for unit testing. I hope that CMake will unify the build on Windows, Linux and MacOS. As for XCode, there must be convenient ways to generate a XCode from a CMake project. And currently, I'm using CMake to generate files for VSCode. VSCode is awesome for reading and writing code in C++. ---- On Tue, 16 Oct 2018 19:48:20 +0800 Massimiliano Gubinelli <***@gmail.com> wrote ---- Personally I just use and maintain the TeXmacs.xcodeproj Xcode project in packages/macos. It rely on the standard configure step for set up and just need some minor tweaks afterwards to be able to compile and debug in Xcode.  What do you think are the advantages of a CMake setup? M On 16. Oct 2018, at 12:02, Darcy Shen <***@zoho.com> wrote: I find that Archlinux already use the CMake Build System. However, there must be small problems in it. And it only works fine on GNU/Linux. As for MacOS, I only use the CMake Build System for developing but not packaging. _______________________________________________ Texmacs-dev mailing list Texmacs-***@gnu.org https://lists.gnu.org/mailman/listinfo/texmacs-dev _______________________________________________ Texmacs-dev mailing list Texmacs-***@gnu.org https://lists.gnu.org/mailman/listinfo/texmacs-dev
Massimiliano Gubinelli
2018-10-16 15:22:48 UTC
Permalink
Post by Darcy Shen
Personally, I have no experience with Xcode. I don't know how to build and package GNU TeXmacs on MacOS. Can you document the minor tweaks? And the Qt version we currently use.
I use Xcode only for development on my machine. Packaging of TeXmacs on Mac goes via the command line:

make BUNDLE

which produces a complete and independent .app package in ../distr/. by bundling all the needed libraries, no need to use Xcode.

I’m not currently using Linux nor Windows, but I think that the current makefile is capable of producing the necessary output files in all these systems.

I’m not very fond of configure/make too but I think this is mandatory for GNU projects. Anyway I think that if you manage to maintan a cmake build system that is nice.

In my opinion however the current Xcode project is ok: it can compile an X11 or a QT version or a Cocoa version without running ./configure again.

The Xcode project does not change often and is not a burden to maintain. It is easier for me to keep it around. I think we are only few which use it regularly.

Good luck for the presentation!

Best
Max
Post by Darcy Shen
https://github.com/texmacs/GNUTeXmacs/commit/fe0b382070e8355426a1356a46bda7b372503cf5 <https://github.com/texmacs/GNUTeXmacs/commit/fe0b382070e8355426a1356a46bda7b372503cf5>
Next Thursday, I will give a talk on GNU TeXmacs for Shanghai Linux User Group. I hope I can distributed my customized TeXmacs.dmg for SHLUG guys to try.
And in my opinion, CMake is better and easier to maintain than our long `configure` file. And I have introduced gtest in CMake for unit testing. I hope that CMake will unify the build on Windows, Linux and MacOS. As for XCode, there must be convenient ways to generate a XCode from a CMake project. And currently, I'm using CMake to generate files for VSCode. VSCode is awesome for reading and writing code in C++.
Personally I just use and maintain the TeXmacs.xcodeproj Xcode project in packages/macos. It rely on the standard configure step for set up and just need some minor tweaks afterwards to be able to compile and debug in Xcode.
What do you think are the advantages of a CMake setup?
M
I find that Archlinux already use the CMake Build System. However, there must be small problems in it. And it only works fine on GNU/Linux. As for MacOS, I only use the CMake Build System for developing but not packaging.
_______________________________________________
Texmacs-dev mailing list
https://lists.gnu.org/mailman/listinfo/texmacs-dev <https://lists.gnu.org/mailman/listinfo/texmacs-dev>
_______________________________________________
Texmacs-dev mailing list
https://lists.gnu.org/mailman/listinfo/texmacs-dev <https://lists.gnu.org/mailman/listinfo/texmacs-dev>
Massimiliano Gubinelli
2018-10-16 15:44:47 UTC
Permalink
Hi,
Post by Darcy Shen
https://github.com/texmacs/GNUTeXmacs/commit/fe0b382070e8355426a1356a46bda7b372503cf5 <https://github.com/texmacs/GNUTeXmacs/commit/fe0b382070e8355426a1356a46bda7b372503cf5>
can you explain precisely what the bug was? That line you removed seems to have been written with some particular purpose so maybe removing it could apriori cause some problem elsewhere.


Best
Max
Darcy Shen
2018-10-16 16:18:52 UTC
Permalink
The commit that added this line will make TeXmacs extremely slow. My commit just revert a part of the changes. TeXmacs 1.99.8 is much slower than 1.99.7.Precisely this 100 added a latency of 100ms.Even if it is expected we should haved documented the magic number 100.---- On Tue, 16 Oct 2018 23:44:47 +0800 Massimiliano Gubinelli<***@gmail.com> wrote ----Hi,On 16. Oct 2018, at 16:07, Darcy Shen <***@zoho.com> wrote:Normally, I just wait for the official release of GNU TeXmacs. But there is a severe bug in GNU TeXmacs 1.99.8. And this is my fix:https://github.com/texmacs/GNUTeXmacs/commit/fe0b382070e8355426a1356a46bda7b372503cf5can you explain precisely what the bug was? That line you removed seems to have been written with some particular purpose so maybe removing it could apriori cause some problem elsewhere.BestMax
Loading...