Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » U++ Developers corner » Looking for windows compiler possibilities
Re: Looking for windows compiler possibilities [message #44860 is a reply to message #44848] Fri, 10 July 2015 10:20 Go to previous messageGo to next message
cbpporter is currently offline  cbpporter
Messages: 1401
Registered: September 2007
Ultimate Contributor
[quote]mirek wrote on Wed, 08 July 2015 10:24
Sgifan wrote on Tue, 07 July 2015 19:01
Why not propose (and adapt The IDE to) using VS2013 community edition

It would be perfect in most situation (legalize wise) and it is C++11.


Not "enough" C++11 unfortunately AFAIK. Things required for pick/clone to work are not there. Anyway, perhaps it is worth workaround.


Isn't && support good enough in the latest free VS?

BTW, are there plans to implement full r-value for String and other classes, like in the case of s + func1() + func2(), or would String not benefit from this since it does RC and other stuff?

Quote:

Quote:

I know that currently the IDE does not work with it, at least that's what I did experience


Autodetect might not work, but I believe that after fixing paths, it should work just fine.

Generally, I agree that we should support this out of box. But it would still be nice to have "complete download".

Mirek

I can confirm that autodetect does not work. Since I installed this version I need to not use the highest version VS available.
Re: Looking for windows compiler possibilities [message #44863 is a reply to message #44860] Fri, 10 July 2015 13:11 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13975
Registered: November 2005
Ultimate Member
[quote title=cbpporter wrote on Fri, 10 July 2015 10:20]Quote:
mirek wrote on Wed, 08 July 2015 10:24
Sgifan wrote on Tue, 07 July 2015 19:01
Why not propose (and adapt The IDE to) using VS2013 community edition

It would be perfect in most situation (legalize wise) and it is C++11.


Not "enough" C++11 unfortunately AFAIK. Things required for pick/clone to work are not there. Anyway, perhaps it is worth workaround.


Isn't && support good enough in the latest free VS?


&& is not enough. We need 'default' for constructors to work correctly.

See http://www.ultimatepp.org/srcdoc$Core$pick_$en-us.html, Composition.

Quote:

BTW, are there plans to implement full r-value for String and other classes, like in the case of s + func1() + func2(), or would String not benefit from this since it does RC and other stuff?


I am considering it, but performance gains will be negligible. In fact, such things only make sense if you do not have to maintain C++03 compatibility (which is the point of this thread).

Quote:

I can confirm that autodetect does not work. Since I installed this version I need to not use the highest version VS available.


Maybe you can fix this and post the patch. Should be easy...

Mirek
Re: Looking for windows compiler possibilities [message #44864 is a reply to message #44863] Fri, 10 July 2015 15:26 Go to previous messageGo to next message
cbpporter is currently offline  cbpporter
Messages: 1401
Registered: September 2007
Ultimate Contributor
mirek wrote on Fri, 10 July 2015 14:11


Maybe you can fix this and post the patch. Should be easy...

Mirek

Yes, I haven't truly contributed a lot of patches lately Smile.

Anyway, the problem is that Microsoft loves to change the directory layout around for no good reason. Simply checking that msc.sdk + "\\lib" exists on disk won't help.

Here is a potential way that fixed bugs for me:

void TestLib() {
		if (create) {			
			if (FindFile(sdk + "\\lib\\*.lib"))
				sdklib = sdk + "\\lib";
			if (FindFile(sdk + "\\lib\\x86\\*.lib"))
				sdklib = sdk + "\\lib\\x86";
			else if (FindFile(sdk + "\\lib\\win8\\um\\x86\\*.lib"))
				sdklib = sdk + "\\lib\\win8\\um\\x86";
			else if (FindFile(sdk + "\\lib\\winv6.3\\um\\x86"))
				sdklib = sdk + "\\lib\\winv6.3\\um\\x86";
		}
		if (create64) {			
			if (FindFile(sdk + "\\lib\\*.lib"))
				sdklib64 = sdk + "\\lib";
			else if (FindFile(sdk + "\\lib\\x64\\*.lib"))
				sdklib64 = sdk + "\\lib\\x64";
			else if (FindFile(sdk + "\\lib\\win8\\um\\x64\\*.lib"))
				sdklib64 = sdk + "\\lib\\win8\\um\\x64";
			else if (FindFile(sdk + "\\lib\\winv6.3\\um\\x64"))
				sdklib64 = sdk + "\\lib\\winv6.3\\um\\x64";
		}
	}


I had to add the sdklib fields to actually determine where the lib files are. I have a ton of VS version installed, and all use different paths...

I'm downloading VS 2015 which for some stupid reason is MSC14 to test that too...
Re: Looking for windows compiler possibilities [message #44868 is a reply to message #44864] Fri, 10 July 2015 16:25 Go to previous messageGo to next message
cbpporter is currently offline  cbpporter
Messages: 1401
Registered: September 2007
Ultimate Contributor
And MSC14 changes things around again: http://blogs.msdn.com/b/vcblog/archive/2015/03/03/introducin g-the-universal-crt.aspx
Re: Looking for windows compiler possibilities [message #44869 is a reply to message #44864] Sat, 11 July 2015 10:41 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13975
Registered: November 2005
Ultimate Member
cbpporter wrote on Fri, 10 July 2015 15:26
mirek wrote on Fri, 10 July 2015 14:11


Maybe you can fix this and post the patch. Should be easy...

Mirek

Yes, I haven't truly contributed a lot of patches lately Smile.

Anyway, the problem is that Microsoft loves to change the directory layout around for no good reason. Simply checking that msc.sdk + "\\lib" exists on disk won't help.

Here is a potential way that fixed bugs for me:

void TestLib() {
		if (create) {			
			if (FindFile(sdk + "\\lib\\*.lib"))
				sdklib = sdk + "\\lib";
			if (FindFile(sdk + "\\lib\\x86\\*.lib"))
				sdklib = sdk + "\\lib\\x86";
			else if (FindFile(sdk + "\\lib\\win8\\um\\x86\\*.lib"))
				sdklib = sdk + "\\lib\\win8\\um\\x86";
			else if (FindFile(sdk + "\\lib\\winv6.3\\um\\x86"))
				sdklib = sdk + "\\lib\\winv6.3\\um\\x86";
		}
		if (create64) {			
			if (FindFile(sdk + "\\lib\\*.lib"))
				sdklib64 = sdk + "\\lib";
			else if (FindFile(sdk + "\\lib\\x64\\*.lib"))
				sdklib64 = sdk + "\\lib\\x64";
			else if (FindFile(sdk + "\\lib\\win8\\um\\x64\\*.lib"))
				sdklib64 = sdk + "\\lib\\win8\\um\\x64";
			else if (FindFile(sdk + "\\lib\\winv6.3\\um\\x64"))
				sdklib64 = sdk + "\\lib\\winv6.3\\um\\x64";
		}
	}



Have you tested inside theide code? Can you provide a tested patch?

Mirek
Re: Looking for windows compiler possibilities [message #44879 is a reply to message #44869] Wed, 15 July 2015 12:45 Go to previous messageGo to next message
cbpporter is currently offline  cbpporter
Messages: 1401
Registered: September 2007
Ultimate Contributor
Not yet, since I am running into the problem of TheIDE nightly not detecting the SDK for MSC11 and 12, but when building with 10, the "ide" I'm running fromwithin TheIDE detects the sdk just fine.
Re: Looking for windows compiler possibilities [message #44956 is a reply to message #44879] Thu, 30 July 2015 13:22 Go to previous messageGo to next message
cbpporter is currently offline  cbpporter
Messages: 1401
Registered: September 2007
Ultimate Contributor
Well I manged to fully mess up my VS and SDKs and nothing is working any more. Not even VS can find the SDK. I need to fully clean my system.

Hopefully a Windows reinstall won't be needed Smile.
Re: Looking for windows compiler possibilities [message #44966 is a reply to message #44956] Mon, 03 August 2015 10:52 Go to previous message
cbpporter is currently offline  cbpporter
Messages: 1401
Registered: September 2007
Ultimate Contributor
cbpporter wrote on Thu, 30 July 2015 14:22
Well I manged to fully mess up my VS and SDKs and nothing is working any more. Not even VS can find the SDK. I need to fully clean my system.

Hopefully a Windows reinstall won't be needed Smile.

Nope, needed to reinstall Windows.

Even after cleanup, VS refused to install correctly so I had to wipe the OS.

It is a really bad idea to install every VS.

Next time I'm doing it in a VM.
Previous Topic: Google code shutting down
Next Topic: Interesting Idea: Stop writing Regular Expressions. Express them with Verbal Expressions.
Goto Forum:
  


Current Time: Thu Mar 28 21:01:00 CET 2024

Total time taken to generate the page: 0.01210 seconds