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 » Community » Coffee corner » Visual Studio (Community) 2017 released
Re: Visual Studio (Community) 2017 released [message #48466 is a reply to message #48450] Wed, 05 July 2017 19:19 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 12565
Registered: November 2005
Ultimate Member
Tom1 wrote on Tue, 04 July 2017 12:47
Hi Koldo,

Not sure if this helps, but I tested the VS2017 BuildTools by duplicating the build method I already had for VS2017 community edition (which was automatically generated by theide). Then I just renamed it and changed the include, lib and bin folders to point at BuildTools instead of the VS community.
Tom


BTW, could you post that .bm here? Just to get me started...
Re: Visual Studio (Community) 2017 released [message #48467 is a reply to message #48466] Wed, 05 July 2017 22:38 Go to previous messageGo to next message
Tom1
Messages: 798
Registered: March 2007
Contributor
Hi Koldo and Mirek,

I had already trashed that installation, but I reinstalled the Visual Studio 2017 Build Tools and reconfigured TheIDE with a suitable BM. Please find it attached. Also, note that this is a 32-bit BM. It uses debugger from the parallel Visual Studio 2017 Community installation because I think there is none included with Build Tools installation.

Best regards,

Tom
  • Attachment: VSBT2017.bm
    (Size: 1.36KB, Downloaded 105 times)
Re: Visual Studio (Community) 2017 released [message #48471 is a reply to message #48466] Thu, 06 July 2017 08:14 Go to previous messageGo to next message
koldo is currently offline  koldo
Messages: 3141
Registered: August 2008
Ultimate Member
Thank you Mirek. This is my BM.

Thank you Tom. A difference with your MSVC install is that your is under c:/program files and mine is under C:\Program Files (x86). Maybe is your OS 32 bits?
  • Attachment: MSC17x64.bm
    (Size: 1.43KB, Downloaded 122 times)


Best regards
Iñaki
Re: Visual Studio (Community) 2017 released [message #48472 is a reply to message #48471] Thu, 06 July 2017 08:41 Go to previous messageGo to next message
Tom1
Messages: 798
Registered: March 2007
Contributor
Hi Koldo,

You are absolutely right. I made it under Windows 10 Pro 32 bit.

Please note that current U++ can auto detect the VS2017 Community installation, while it cannot auto detect VS2017 Build Tools installation at this time. I have a strong feeling that this will change pretty soon now since Mirek indicated interest in this. I think the compiler is exactly the same, but Build Tools lacks debugger and IDE compared to a full VS2017 Community installation. (So installing VS2017 Community already includes everything needed and is also readily auto detected with current U++.)

Best regards,

Tom



Re: Visual Studio (Community) 2017 released [message #48474 is a reply to message #48472] Thu, 06 July 2017 09:30 Go to previous messageGo to next message
cbpporter is currently offline  cbpporter
Messages: 1400
Registered: September 2007
Senior Contributor
I see MS are as bad as ever with consistency and their naming schemes. I have not yet bothered with 2017, but I guess I need to install it.

A bit of a pain since I use and regularly test for MSC10, MSC12 and MSC15. Now I'll have MSC17 too Smile.
Re: Visual Studio (Community) 2017 released [message #48476 is a reply to message #48472] Thu, 06 July 2017 10:04 Go to previous messageGo to next message
Tom1
Messages: 798
Registered: March 2007
Contributor
Hi,

Just for completeness, please find attached both 32 and 64 bit BM files for Visual Studio 2017 Build Tools created on Windows 10 Professional 64 bit OS.

Best regards,

Tom
Re: Visual Studio (Community) 2017 released [message #48477 is a reply to message #48471] Thu, 06 July 2017 10:11 Go to previous messageGo to next message
Tom1
Messages: 798
Registered: March 2007
Contributor
Hi Koldo,

I just took a closer look and found that your MSC17x64.bm file also had PATH and LIB references pointing at VS2017 Community. Only INCLUDE was pointing to BuildTools. This may explain if you had issues with your BM when trying to use BuildTools instead of Community.

Best regards,

Tom

Re: Visual Studio (Community) 2017 released [message #48478 is a reply to message #48477] Thu, 06 July 2017 16:15 Go to previous messageGo to next message
koldo is currently offline  koldo
Messages: 3141
Registered: August 2008
Ultimate Member
Tom1 wrote on Thu, 06 July 2017 10:11
I just took a closer look and found that your MSC17x64.bm file also had PATH and LIB references pointing at VS2017 Community. Only INCLUDE was pointing to BuildTools. This may explain if you had issues with your BM when trying to use BuildTools instead of Community.
Thank you Tom, you are right!

The only problem is that I have not found any devenv.exe under Microsoft Visual Studio\2017.

However TheIDE seems to compile and debug Smile


Best regards
Iñaki
Re: Visual Studio (Community) 2017 released [message #48480 is a reply to message #48478] Thu, 06 July 2017 19:07 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 12565
Registered: November 2005
Ultimate Member
MS Build Tools now supported by auto setup.

BM names changed to MSVS15, MSVS17, MSBT17
Re: Visual Studio (Community) 2017 released [message #48485 is a reply to message #48480] Fri, 07 July 2017 09:16 Go to previous messageGo to next message
koldo is currently offline  koldo
Messages: 3141
Registered: August 2008
Ultimate Member
Perfect.

In my case, with BuildTools, _MSC_FULL_VER reports
- 191025019 for MSC17x64
- 190023026 for MSC15x64


Best regards
Iñaki
Re: Visual Studio (Community) 2017 released [message #48486 is a reply to message #48485] Fri, 07 July 2017 10:14 Go to previous messageGo to next message
Tom1
Messages: 798
Registered: March 2007
Contributor
Hi,

I can confirm that the 64 bit TheIDE 11218 correctly autoconfigured both x86 and x64 build methods for VS 2015, VS 2017 and BT 2017. This was on Windows 10 Pro 64.

Thanks and best regards,

Tom
Re: Visual Studio (Community) 2017 released [message #48488 is a reply to message #48486] Fri, 07 July 2017 17:45 Go to previous messageGo to next message
rafiwui is currently offline  rafiwui
Messages: 105
Registered: June 2017
Location: Stuttgart, Germany
Experienced Member
Well I can't confirm it on my home PC but I can confirm it on my work PC.

But I have to say my setup at home is a bit lets say "special" Laughing

Windows 10 64bit is installed on C:\
Visual Studio 2017 Community is installed on a secondary SSD (E:\Programs\Visual Studio 2017 Community)
Finally U++ is unzipped on another secondary HDD (D:\Programs\U++\upp)

When I start TheIDE the first time you see for a short time that it is doing sth about build methods but then continues and nothing is created. When I tried installing the new nightly at work today this was longer and the correct .bm files were created.

So I guess the installer just can't connect my 3 drives Sad Or is it windows and the methods from the WinAPI which are getting called? (I did not take a deeper look inside the files so I can't tell)

Can someone upload a newly created MSVS2017.bm/MSVS2017x64.bm for me so I can set the paths correct?

Greetings
Daniel


Greetings
Daniel
Re: Visual Studio (Community) 2017 released [message #48506 is a reply to message #48488] Tue, 11 July 2017 09:06 Go to previous messageGo to next message
Tom1
Messages: 798
Registered: March 2007
Contributor
Hi,

Sorry for the delay. Here are the BMs (auto-generated by TheIDE 11218) for Visual Studio 2017 Community and also Visual Studio 2017 Build Tools.

Best regards,

Tom
Re: Visual Studio (Community) 2017 released [message #48509 is a reply to message #48506] Tue, 11 July 2017 19:00 Go to previous messageGo to next message
rafiwui is currently offline  rafiwui
Messages: 105
Registered: June 2017
Location: Stuttgart, Germany
Experienced Member
Thanks for the files. But it does not work. TheIDE tells me when I try to compile:
c:\program files (x86)\windows kits\10\include\10.0.15063.0\um\winsock2.h (882): fatal error C1083: Cannot open include file: 'qos.h': No such file or directory

There is no file 'qos.h' in the folder c:\program files (x86)\windows kits\10\include\10.0.15063.0\um. Should it be there?

And another thing: In your MSVS17x64 there is this line:
PATH = "...;c:/program files (x86)/windows kits/10/bin/x86;...;

Shouldn't it be:
PATH = "...;c:/program files (x86)/windows kits/10/bin/x64;...;

??


Greetings
Daniel
Re: Visual Studio (Community) 2017 released [message #48513 is a reply to message #48509] Wed, 12 July 2017 11:19 Go to previous messageGo to next message
Tom1
Messages: 798
Registered: March 2007
Contributor
Hi,

The files I uploaded are just the ones my U++ installation have auto-created on my platform. I wouldn't necessarily expect them to work on your system without modification. I just uploaded them for you as a template. If you find similar paths on your system, you can then tune these files accordingly to match your system configuration.

I have no knowledge of the automatic build method generation, so I cannot help on that part. Certainly having unusual installation paths can affect such code.

The reference to x86 in the PATH does not appear to cause any trouble on my 64-bit system. The reason for it is unknown to me.

I wish you the best of luck!

Best regards,

Tom

Re: Visual Studio (Community) 2017 released [message #48517 is a reply to message #48513] Wed, 12 July 2017 21:39 Go to previous messageGo to next message
rafiwui is currently offline  rafiwui
Messages: 105
Registered: June 2017
Location: Stuttgart, Germany
Experienced Member
Ok I found the problem. Somehow in the include folder of the newest windows sdk (c:/program files (x86)/windows kits/10/include/10.0.15063.0/...) some files are missing (qos.h is one of them). So I guess your files are working (thanks for giving me them) but I have to check my visual studio for updates or repairing my sdk.

Greetings
Daniel
Re: Visual Studio (Community) 2017 released [message #48538 is a reply to message #48517] Mon, 17 July 2017 15:47 Go to previous messageGo to next message
rafiwui is currently offline  rafiwui
Messages: 105
Registered: June 2017
Location: Stuttgart, Germany
Experienced Member
Ok the problem was my VS2017. It wasn't up to date with the newest Win10 SDK. Working perfectly fine now.

Greetings
Daniel
Re: Visual Studio (Community) 2017 released [message #48651 is a reply to message #48506] Sun, 13 August 2017 21:57 Go to previous messageGo to next message
forlano is currently offline  forlano
Messages: 1105
Registered: March 2006
Location: Italy
Experienced Contributor
Tom1 wrote on Tue, 11 July 2017 09:06

Sorry for the delay. Here are the BMs (auto-generated by TheIDE 11218) for Visual Studio 2017 Community and also Visual Studio 2017 Build Tools.


Hello,

today I have installed U++ 11300 and VS2017 community on a 64 bit machine with windows 7.
I looked for a bm file because my theide was not able to produce one via automatic build method setup.
Then I used your MSVS17x64.bm file but I had to rename it MSC17x64.bm to avoid an "invaild build method".
Not it seems to compile as usual.

However it didn't produce an exe file. Surprised
It stopped at processing a .rc file.
Reading the forum I have understood my installation has not the rc.exe program, so I missed to download something.
Does anybody know (see picture) what have I to download to have a U++ working setup.

Thanks,
Luigi
index.php?t=getfile&id=5380&private=0
  • Attachment: rc.png
    (Size: 112.15KB, Downloaded 483 times)
Re: Visual Studio (Community) 2017 released [message #48652 is a reply to message #47733] Mon, 14 August 2017 07:03 Go to previous messageGo to next message
deep is currently offline  deep
Messages: 221
Registered: July 2011
Location: Bangalore
Experienced Member
Hi Luigi,

I think you will require this additionally.

https://developer.microsoft.com/en-US/windows/downloads/wind ows-10-sdk


Warm Regards

Deepak
Re: Visual Studio (Community) 2017 released [message #48653 is a reply to message #48652] Mon, 14 August 2017 08:58 Go to previous messageGo to previous message
rafiwui is currently offline  rafiwui
Messages: 105
Registered: June 2017
Location: Stuttgart, Germany
Experienced Member
That is correct. You need the Win10 SDK. But you can select it in the VS installer directly. If you can't find it on the first tab. Search it in the single components tab and select it.

Greetings
Daniel
Previous Topic: Web Assembly... Compiling U++ code to run in the web browser...
Next Topic: Nightly build versioning
Goto Forum:
  


Current Time: Thu Jul 02 12:11:00 CEST 2020

Total time taken to generate the page: 0.01082 seconds