DCPU-16 toolchain (all in one)

Re:DCPU-16 toolchain (all in one) by drivebyacct2 on Monday April 30, 2012 @04:54AM (#3908512)

I can't remember the last time I struggled building something on a random distribution that worked on another. What are you doing that you run into incompatibilities across modern Linux distributions?

It's certainly better than: "use VS" or "suffer through any other sort of Windows dev" in my opinion.

[ Parent | on HN ]

Re:DCPU-16 toolchain (all in one) by lmm on Monday April 30, 2012 @07:02AM (#3908723)

I'm constantly running into incompatibilities with my own code, all of them due to Debian. The one that's still causing me trouble is being able to invoke a pyuic4 that has access to both pykde and pyqwt; as far as I can tell that's impossible on Debian.

[ Parent | on HN ]

Re:DCPU-16 toolchain (all in one) by pjmlp on Monday April 30, 2012 @05:03AM (#3908530)

- Packaging

- Default installation directories

- so Dependencies

Regarding your comment, there are many other ways to develop software for Windows besides VS.

[ Parent | on HN ]

Re:DCPU-16 toolchain (all in one) by drivebyacct2 on Monday April 30, 2012 @05:08AM (#3908537)

The third is the only that's tangentially related to the development pains we're discussing here. Packaging is a "fun" issue, but it's apples and oranges with multiple compatibility layers to get to a common denominator to be able to ... build a DCPU toolchain for example.

>Regarding your comment, there are many other ways to develop software for Windows besides VS.

Uh huh, and as seen even... right here... it's normally a (relatively) major pain in the ass to orchestrate.

[ Parent | on HN ]