Author Topic: Compiling in VS2017 creates folder outside project folder  (Read 216 times)

0 Members and 1 Guest are viewing this topic.

Offline Yarn

  • 210
Compiling in VS2017 creates folder outside project folder
I installed Visual Studio 2017 recently and noticed that whenever I compile FSO, a folder named either Win32 or x64 (depending on what architecture the project was created for) is created just outside the project folder. The folder's structure resembles that of the identically named folder that gets created within the project folder, though the files are different.

I'm pretty sure this never happened with Visual Studio 2015.
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178

 

Offline The E

  • He's Ebeneezer Goode
  • Global Moderator
  • 213
  • Nothing personal, just tech support.
    • Skype
    • Steam
    • Twitter
Re: Compiling in VS2017 creates folder outside project folder
Are you using the solution files or VS2017's built-in CMAKE support?
**** every cause that ends in murder and children crying. ― Iain Banks
Join the fun at the HLP IRC channel. Get the latest spam and gossip as long as it's fresh!

 

Offline Yarn

  • 210
Re: Compiling in VS2017 creates folder outside project folder
I'm using CMake 3.7.2 to make the solution (for VS2017, of course) and then opening that in Visual Studio 2017.
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178