DCPU-16 toolchain (all in one)

Re:DCPU-16 toolchain (all in one) by Deestan on Monday April 30, 2012 @04:46AM (#3908495)

Having "spent the effort" over and over again, I fully understand why hobbyists don't bother:

The Proper Way on Windows is a largely undocumented minefield strewn with broken glass and lack of a sane package managing system.

Personally, I require payment to even bother.

[ Parent | on HN ]

Re:DCPU-16 toolchain (all in one) by pjmlp on Monday April 30, 2012 @04:50AM (#3908500)

From my experience of doing software development professionally in several flavors of UNIX and Windows systems, I would say Linux is no better as there is seldom a way that works flawlessly across distributions.

[ Parent | on HN ]

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 ]

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

Can you elaborate? If there is a better way to do this, please do say or link to a pull request for the project...

[ Parent | on HN ]

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

- Provide proper plugins to Programmers Notepad

- Make use of a proper IDE like Code::Blocks

[ Parent | on HN ]

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

... I can't tell if you don't understand what the issue is here (from this post and your others), or if you really think that forcing complex workarounds into one-off IDEs is a good way to solve this problem.

[ Parent | on HN ]

Re:DCPU-16 toolchain (all in one) by pjmlp on Monday April 30, 2012 @06:57AM (#3908712)

I am playing a bit devil's advocate, probably with not so much success.

The thing is, that each operating system has it own way of doing things, and many people in open source tend to think that everywhere else should be like GNU/Linux.

I used to think like that, until I got the opportunity to work with several different types of operating systems, all UNIX flavours, Windows, OS/400, Symbian, VMS and see that there are many ways to do certain things.

Here is an example how someone else did a Windows based development environment for DCPU,

http://0x10c-devkit.com/

[ Parent | on HN ]