News for hackers. Stuff that matters.
Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by malkia on Tuesday January 02, 2018 @04:16PM (#16055730)
Currently I'm doing C++ with Qt, sometimes C# (game dev under Windows), but was at Google just few months ago doing Java.

While Qt is great, we've been running into logistic problems - like we have plenty of tools that use it, and we are forced to place all the binaries into one folder ("bin"), and the Qt dlls there for legal reasons, license, but buying the license for static linking won't be a problem for us reallly. The real problem is that once we link our binaries statically, then our plugins that also use Qt won't work with them, unless we do some magic, and forward all QtXxx.dll end points to be from the main executable, or use more abstract interfaces - e.g. our plugins should not use Qt directly.

Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by jcelerier on Wednesday January 03, 2018 @05:50AM (#16059993)
> but buying the license for static linking won't be a problem for us reallly.

You can statically link with LGPL code, as long as you provide a means to relink (typically, shipping .o files if requested).

https://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynami...

Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by kodablah on Tuesday January 02, 2018 @04:28PM (#16055873)
I likewise have used these. Qt (really C++) development in general suffers from annoyingly slow compile times in my experience. Also, once you go beyond anything trivial, .pro files become complicated as do build systems around them.
Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by malkia on Tuesday January 02, 2018 @04:42PM (#16055999)
We don't use .pro files or QtCreator - it's Visual Studio + custom build rules. Still slow, and nasty with generation.

As build system, we used to have IncrediBuild, but since we are PS4 developers we get SN-DBS for free - http://www.snsys.com/products/SN-DBS.asp - it speeds up the build, but once the Qt moc/etc rules come in, the build needs to wait for these to be generated, and then proceeds.

There are ways to overcome this, and we are looking into improving this.

I've tried using .pro files, but first, I can't sell them to the rest of the engineers, as pretty much almost everyone knows Visual Studio, .sln/.vcxproj files. There are some ideas about alternative build systems, but not there yet. (at the end most of these just generate .sln/.vcxproj, like CMake, or premake, etc.).

Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by kodablah on Tuesday January 02, 2018 @04:47PM (#16056044)
My application is cross platform. So I use .pro files + qmake, then make/nmake. As I started needing to move files around in cross platform ways, I just maintain a Go script now that does the build. Tired of custom DSLs and having to dig deep into build-system-specific things (e.g. Groovy w/ Gradle and the confusion around what code runs when like defs vs tasks, doFirst, etc).
Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by malkia on Tuesday January 02, 2018 @04:51PM (#16056079)
Try using "jom" as replacement for nmake - it's done by Qt themselves, and it's much better! - https://wiki.qt.io/Jom
Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by ateesdalejr on Tuesday January 02, 2018 @05:02PM (#16056184)
I agree on the using some other language to do builds instead of using a complicated build process. Python is sufficient enough for me.
Re:Using Java 9 Modularization to Ship Zero-Dependency Apps by zura on Tuesday January 02, 2018 @05:22PM (#16056378)
Why do you need to link statically?