Originally posted by prodigy_
View Post
Announcement
Collapse
No announcement yet.
C4 Engine Drops Linux Support, Calls It "Frankenstein OS"
Collapse
X
-
-
Originally posted by johnc View PostBest thing to do is pick up a small used SSD on eBay and just install Ubuntu plain to that. Put GRUB on there, and leave the Windows drive completely untouched. Worst case if GRUB shits the bed, you can just boot to the Windows drive using the BIOS hot key.
Comment
-
Originally posted by asdfblah View PostWhy the visceral response? You don't seem to have understood my reply. I know well what RMS (and Linus) have done, I'm not saying they are incompetent. Quite the contrary, I'm saying that installing linux can be a PITA and a waste of time. Go read my replies and think again, "mate".
When a nvidia blob installer would make the ui not start up or just windows not start up after using it, would you blaim microsoft for it.
Nobody hinders Nvidia on making a install-blob.bin thing that 100% of the times works and all features are there... how is that linux problem, nvidia dont need included packages to the distro or do they have the newest drivers included in windows all the time? NO.
Just dont compare always linux to a perfect world and windows is just autojmaticly good enough, cant hear that anymore.
Comment
-
I am a cross-platform developer for a proprietary program which runs on GNU/Linux, Windows and Mac OSX.
It sure isn't easy to write cross-platform software, especially when it isn't just a simple GUI application, but it's not impossible. GNU/Linux is a great platform in my opinion, but it does have its flaws.
The only real problem I encounter as a proprietary software developer is library dependency issues... which isn't exactly easy to solve compared to Windows.
To compare:
On Windows, I compile my program and all my dependencies, pack my exe and dlls into an installer (or zip file) and I'm done. This compiled program + dependencies will work on Windows XP up until Windows 8 (and possibly 9 and 10 in the future).
On GNU/Linux I use the package manager to install all (or most) dependencies, compile my program and then the dependencies, tarball it, then I'm done(*).
*There are a few catches, though:
1. The user will have to use the same distribution that I compile my program on. Otherwise there may be GLIBC issues (too old version), or the libraries are named differently and the user will have to symlink...
2. The user will have to manually install the dependencies using his package manager.
3. If a library is not available in the repository, the user will have to compile and install it.
It's a lot more work for the user to get our program up and running in comparison to Windows.
We're a small development team so we can not compile, package, and test on all major distributions (Ubuntu, Mint, Debian, Fedora, OpenSUSE, RHEL, CENTOS, etc.). It would simply be too time consuming.
It would be great if supporting many distributions would be as easy as supporting different versions of Windows, i.e compile once and ship all the library dependencies with your proprietary program.
I can't disclose any information about our proprietary program, in case someone was wondering.
Comment
-
Originally posted by AnonymousCoward View PostOn Windows, I compile my program and all my dependencies, pack my exe and dlls into an installer (or zip file) and I'm done. This compiled program + dependencies will work on Windows XP up until Windows 8 (and possibly 9 and 10 in the future).
On GNU/Linux I use the package manager to install all (or most) dependencies, compile my program and then the dependencies, tarball it, then I'm done(*).
*There are a few catches, though...)
Compile your program (on a sufficiently old distro version), pack the binary + the dependent libs into a zip or whatever. Include a simple script to run the program:
Code:#!/bin/bash cd "`dirname $0`" LD_LIBRARY_PATH=$LD_LIBRARY_PATH:./lib ./binary
Then when the user unpacks this, assuming he has a newer glibc and the architecture is ok (64bit/32bit), then the program will run and use system libs first or if they're not installed then the libs that you provided (just be sure to provide the dependencies of your dependencies too - it's generally a good idea to not use too many libs, better stick with 1 fairly complete framework). The only thing this differs from your windows example is the script to set the LD_LIBRARY_PATH for the binary.
No need to thank me ;-).
Comment
-
Originally posted by AnonymousCoward View PostWe're a small development team so we can not compile, package, and test on all major distributions (Ubuntu, Mint, Debian, Fedora, OpenSUSE, RHEL, CENTOS, etc.). It would simply be too time consuming.
Originally posted by blackiwid View Postyes like every other os too... except linux is less pain then installing windows. so what do we need to do offer absolutly no pain vs heavy pain installing windows to be good enough?
Originally posted by AnonymousCoward View PostWhen a nvidia blob installer would make the ui not start up or just windows not start up after using it, would you blaim microsoft for it.
Nobody hinders Nvidia on making a install-blob.bin thing that 100% of the times works and all features are there... how is that linux problem, nvidia dont need included packages to the distro or do they have the newest drivers included in windows all the time? NO.
And yes, you can say windows has latest drivers included. It is done via windows update. Usually you do not need to download driver to get max resolution supported by your gpu. Package managers on linux do good job there also though.
Originally posted by AnonymousCoward View PostJust dont compare always linux to a perfect world and windows is just autojmaticly good enough, cant hear that anymore.
Comment
-
Originally posted by Kano View PostYou don't need to do a full install of another distro, you can use 32/64 bit chroot as well if you only want to compile it.Originally posted by Cyber Killer View PostFixed that for you:
Compile your program (on a sufficiently old distro version)
Comment
-
Originally posted by bitman View PostAnd how is it a fix? Its ugly workaround for problem that should not exist. For some reason we have no problems building stuff on windows7 for xp. Also as if it was simple to build on old distro. How about i want 10 years old distro support? How about compiler being too old? How about libs too old? How about repos down? Its a joke, not a solution. Same problems stand for chroot.
This is the way GNU/Linux is designed, live with it or recompile everything by hand.
Comment
-
Originally posted by Cyber Killer View PostIf a distro is so old that it's repos aren't available any more then nobody sane is using it anyway. As for lib versions - that is a project planning problem - you should stick to the lib features that are provided by library versions which are available on the oldest system that you are supporting. No, you don't get to pull that developer stunt of using the new and shiny features which have been just released in the new library version.
This is the way GNU/Linux is designed, live with it or recompile everything by hand.
Comment
Comment