5 ms·

Interesting to see that a number of complaints have been levelled against the build systems. It shows just how careful maintainers should be about creating smo

by demarq 12y ago

Interesting to see that a number of complaints have been levelled against the build systems. It shows just how careful maintainers should be about creating smoother build experiences. Anyway I hope the author of the article will post a follow up with his new library.

chris_wot 12y ago
That is 100% the reason why Libreoffice has taken often leave Apache OpenOffice in the dust. Seriously.
- vog 12y ago
  Interesting idea. Do you have any evidence for that theory?
  - chris_wot 12y ago
    Ever tried to build Apache Open Office?
to3m 12y ago
Without a hint of irony, the very next section complains about RtAudio, which has everything in one file to fix exactly this problem ;) (And it's only 10,000 lines.)
- CAMLORN 12y ago
  10000 lines is twice the size of my whole library, but half my library codes itself from a Yaml description (there were good reasons for this; it's actually worked out really, really well). I don't honestly care if the build process is a little awful. I'll deal, if it works on my platform. Having to read an entire 10000 line source file to build up familiarity with the library before fixing it bothers me much more and, if it's still going to need a build step, stopping at "no external dependencies" ought to be enough. I place great stock in the organization of my files as well as my code, and rarely let them go above 1000 lines each. Perhaps this is a weakness.
  - demarq 12y ago
    >I don't honestly care if the build process is a little awful. I'll deal, if it works on my platform. My hopes have just been dashed. I was really hoping you'd make a smooth cross platform build system top of your list. I still wish you all the best anyway.
CAMLORN 12y ago
I'm in the final stages of development, the point where it needs to be tested in real software. I'm also approaching the point of some cool demos. I'm working on something that I've not seen or really heard of in other libraries for this kind of stuff, but going into it needs the wave files and an article, not a brief comment here. nevertheless, there will certainly be followups. Also, complaining about the build systems is hypocritical. Mine requires CMake and something like 5 Python packages--I generate half my code by crawling my own headers and a Yaml file describing my library. This makes the build system a little inconvenient but, among other things, lets me spit out automatically maintained language bindings that are far above what Swig would give. Which is also something I need to write a blog post about.

by demarq 12y ago

chris_wot 12y ago

That is 100% the reason why Libreoffice has taken often leave Apache OpenOffice in the dust. Seriously.

vog 12y ago
Interesting idea. Do you have any evidence for that theory?
- chris_wot 12y ago
  Ever tried to build Apache Open Office?

to3m 12y ago

Without a hint of irony, the very next section complains about RtAudio, which has everything in one file to fix exactly this problem ;) (And it's only 10,000 lines.)

CAMLORN 12y ago
10000 lines is twice the size of my whole library, but half my library codes itself from a Yaml description (there were good reasons for this; it's actually worked out really, really well). I don't honestly care if the build process is a little awful. I'll deal, if it works on my platform. Having to read an entire 10000 line source file to build up familiarity with the library before fixing it bothers me much more and, if it's still going to need a build step, stopping at "no external dependencies" ought to be enough. I place great stock in the organization of my files as well as my code, and rarely let them go above 1000 lines each. Perhaps this is a weakness.
- demarq 12y ago
  >I don't honestly care if the build process is a little awful. I'll deal, if it works on my platform. My hopes have just been dashed. I was really hoping you'd make a smooth cross platform build system top of your list. I still wish you all the best anyway.

CAMLORN 12y ago

I'm in the final stages of development, the point where it needs to be tested in real software. I'm also approaching the point of some cool demos. I'm working on something that I've not seen or really heard of in other libraries for this kind of stuff, but going into it needs the wave files and an article, not a brief comment here. nevertheless, there will certainly be followups. Also, complaining about the build systems is hypocritical. Mine requires CMake and something like 5 Python packages--I generate half my code by crawling my own headers and a Yaml file describing my library. This makes the build system a little inconvenient but, among other things, lets me spit out automatically maintained language bindings that are far above what Swig would give. Which is also something I need to write a blog post about.