The f*** is with the building instructions wiki for win?
Moderator: Moderators
Re: The fuck is with the building instructions wiki for win?
I added:
Of the active developers nobody uses windows for developing. So they might not be able to help as good as on Linux.
which as far I understood is the real reason?
Think it is ok to have such small warning and like this it seems neutral enough.
Experienced peoplepersons can just ignore it and will probally do ok on their own anyway. For less experienced it might be good to know on which plattform they can expect more support/answers to questions.
Abma once patiently guided through with compiling on windows.
Problems were:
-did not work with Visual Studio
-it was very slow. Not idea what speed to expect from old dual core PC without SSD, but it was something like an hour/hours.
If it had been faster on linux I do not know yet.
Of the active developers nobody uses windows for developing. So they might not be able to help as good as on Linux.
which as far I understood is the real reason?
Think it is ok to have such small warning and like this it seems neutral enough.
Experienced peoplepersons can just ignore it and will probally do ok on their own anyway. For less experienced it might be good to know on which plattform they can expect more support/answers to questions.
Abma once patiently guided through with compiling on windows.
Problems were:
-did not work with Visual Studio
-it was very slow. Not idea what speed to expect from old dual core PC without SSD, but it was something like an hour/hours.
If it had been faster on linux I do not know yet.
- KingRaptor
- Zero-K Developer
- Posts: 838
- Joined: 14 Mar 2007, 03:44
Re: The fuck is with the building instructions wiki for win?
Super Mario wrote:I'm sorry, but that final reason listed on the wiki just made me explode here. If it isn't written by the engine devs themselves than I am severely apology for what I did. It just that the "philosophy" reason itself, it... just... so... stupid... it like a linux fanboy free software foundation follower with no coding experience just wrote that which have no part in the build instructions and turn it into a platform for advocating Linux, which I had enough of their crap on the internet as it is.
You know, most people save their rage for something more significant than a single throwaway line at the end of a bullet list that is of ultimately no consequence even within the community for whom it was written.I. just. explain. why I was so upset when I wrote that, but you didn't read that part and just label as "bullshit reasoning".Mario, there was no reason to make a post that ragey.
(This is the nice version of what I wanted to post. The not-nice version would have been an insult spanning no more than eight words.)
Re: The fuck is with the building instructions wiki for win?
TLDR: Windows compiling isn't sane/the best/optimal/(working?)
What can we do about it other than simply saying we need windows developers?
What can we do about it other than simply saying we need windows developers?
Re: The fuck is with the building instructions wiki for win?
I m a valve fanboi, which was founded by guys from microsoft. So by definition im biased when it comes to recommending a OS as a refined User-Experience.
I also argued in the past that the opensource world has some big issues, one of them beeing the "Everyone can learn to be a comp-sience-student" attitude. Which they would hate with a passion, the moment there bakerman would show it in the morning. "Here is some flour, water, and a oven. Get your own free bread, all you can eat."
But they also have some excellent points. One is, that the OS acts as a filter, for the more experienced people you need for real hitec.
This is not the sort of coding for lua/.NET or jdk, were you hit autocomplete, and some magic pixy dwarf shows up, handing you the most fitting algo and datastructure on a tray. And you blindly trust them.
Not auto-pilot here, who un-teaches you how to start, land and fly.
You will meet the natural state of technology here, which is- it aint working. 300 Attempts and counting.
Your first patch might be rejected.
Or get worked over.
With kind words rejected.
With good reasons worked over.
If you want to get help, you will not find tutorials. Not the kind of well chewed through, done for a big audience tutorials.
You will find rarely read papers and even rarer examples of people doing good jobs at what you are trying.
Call it elitism, and you are partially right. But its the sort of open-door elitism, that is always inviting, and always helping. With some sort of budhistic patience for those who try and catch themselves.
I also argued in the past that the opensource world has some big issues, one of them beeing the "Everyone can learn to be a comp-sience-student" attitude. Which they would hate with a passion, the moment there bakerman would show it in the morning. "Here is some flour, water, and a oven. Get your own free bread, all you can eat."
But they also have some excellent points. One is, that the OS acts as a filter, for the more experienced people you need for real hitec.
This is not the sort of coding for lua/.NET or jdk, were you hit autocomplete, and some magic pixy dwarf shows up, handing you the most fitting algo and datastructure on a tray. And you blindly trust them.
Not auto-pilot here, who un-teaches you how to start, land and fly.
You will meet the natural state of technology here, which is- it aint working. 300 Attempts and counting.
Your first patch might be rejected.
Or get worked over.
With kind words rejected.
With good reasons worked over.
If you want to get help, you will not find tutorials. Not the kind of well chewed through, done for a big audience tutorials.
You will find rarely read papers and even rarer examples of people doing good jobs at what you are trying.
Call it elitism, and you are partially right. But its the sort of open-door elitism, that is always inviting, and always helping. With some sort of budhistic patience for those who try and catch themselves.
Re: The fuck is with the building instructions wiki for win?
Example:
I'm using and FreeBSD beside Windows. 10th version will drop GCC. This means for the first time since ~9 years I'll do a fresh installation. This also means that there's 80-85% probability that I'll stop using GCC. Building Spring requires GCC, yes?
I'm using and FreeBSD beside Windows. 10th version will drop GCC. This means for the first time since ~9 years I'll do a fresh installation. This also means that there's 80-85% probability that I'll stop using GCC. Building Spring requires GCC, yes?
Re: The fuck is with the building instructions wiki for win?
Thats an example for what?
some time ago spring could be built with clang, current development branch seems to not compile because of some clang bug / missing feature (?), see http://buildbot.springrts.com/builders/ ... logs/stdio
if you have a more up-to date clang then it maybe compiles.
some time ago spring could be built with clang, current development branch seems to not compile because of some clang bug / missing feature (?), see http://buildbot.springrts.com/builders/ ... logs/stdio
if you have a more up-to date clang then it maybe compiles.
Re: The fuck is with the building instructions wiki for win?
clang will never sync online
Re: The fuck is with the building instructions wiki for win?
For whatever you want ...abma wrote:Thats an example for what?
Re: The fuck is with the building instructions wiki for win?
Is it feasible to build with clang on all platforms though? The LLVM toolchain is up and running on Windows and most of OS X is compiled with it these days
Re: The fuck is with the building instructions wiki for win?
Id be currious to see how a linux build with LLVM would perform, but probably wouldnt make that much of a change i guess.
Is or will LLVM be a supported compiler?
Is or will LLVM be a supported compiler?
Re: The fuck is with the building instructions wiki for win?
no and no
if at all it is an option for development, it will _never_ sync (except someone is willing to spend a month in testing all argument, version, os combinations).
if at all it is an option for development, it will _never_ sync (except someone is willing to spend a month in testing all argument, version, os combinations).
Re: The fuck is with the building instructions wiki for win?
Spring executables from different compilers won't sync with each other, but if both communication partners used the same compiler they might sync.
I'm curious if someone tested [single player] performance with llvm/clang or icc vs gcc?
I'm curious if someone tested [single player] performance with llvm/clang or icc vs gcc?
Re: The fuck is with the building instructions wiki for win?
i would think clang is slightly slower, difference shouldn't be noticeable. you maybe see a small differecence in numbers.dansan wrote:I'm curious if someone tested [single player] performance with llvm/clang or icc vs gcc?
maybe see these articles:
http://www.phoronix.com/scan.php?page=a ... llvm_clang
http://www.phoronix.com/scan.php?page=a ... _compilers
imo we don't have the manpower / time to switch to clang atm. it will cause way to much trouble and maybe it doesn't work at all.
benefits would be pretty small. contributions are welcome, but imo this is nothing we should implement / work on atm.
Re: The fuck is with the building instructions wiki for win?
Thank you - was just curiosity :)