VS Arduino - Compile File Locations

May 2^nd, 2025 at 5:49pm (UTC)

Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

Save the new Output to a Text File and....

Support requests without the output above may be impossible to answer, so please help us to help you

‹ Previous Topic | Next Topic ›

Pages: 1

Compile File Locations (Read 2357 times)

davidcoward Junior Member Offline Posts: 56 Joined: Oct 5^th, 2012	Compile File Locations Apr 19^th, 2018 at 10:19am	Print Post
	Hi I wondered if it might be possible to get better control of the file locations where the application is compiled and linked. I know you can see where the output ends up, but I'm not sure if you can control it. At the moment, it is in Application Data. After compile, I will open the directory and generally rename the hex to contain the version number, eg 141_blinky.hex. The issues I have is that the contents of the directory are destroyed from time to time, so I lose earlier versions (I'm sure this didn't start happening until recently), and application data is not backed up (as there's generally no need to do that). So what I'm asking is if there is a way to put the compiled hex somewhere else, for example in a "HEX" directory with the .ino and other files. Then it would not be destroyed and included in regular backups. Thanks David


	IP Logged

Tim@Visual Micro Administrator Offline Posts: 12186 Location: United Kingdom Joined: Apr 10^th, 2010	Re: Compile File Locations Reply #1 - Apr 19^th, 2018 at 11:47am	Print Post
	Before I answer and to avoid confusion, it helps to be clear about what you think think the final output directory is? You should also say which IDE you are using and which board/architecture?
	« Last Edit: Apr 19^th, 2018 at 11:49am by Tim@Visual Micro »

	WWW Facebook Twitter YouTube IP Logged

davidcoward Junior Member Offline Posts: 56 Joined: Oct 5^th, 2012	Re: Compile File Locations Reply #2 - Apr 19^th, 2018 at 11:57am	Print Post
	The "final output directory" I refer to is this one: Build Folder: file:///C:/Users/David/AppData/Local/Temp/VMBuilds/Blink/teensy31/Debug I'm using VS2017 and most of my stuff is done for Teensies.


	IP Logged

Tim@Visual Micro Administrator Offline Posts: 12186 Location: United Kingdom Joined: Apr 10^th, 2010	Re: Compile File Locations Reply #3 - Apr 19^th, 2018 at 12:14pm	Print Post
	Okay that's the build folder and it is correct that files are deleted from there. The final output folder is below the project in a sub folder with the same name as the current configuration such as \Debug \Release. The files are copied to the final output after a successful build and as long as they are not read-only they should be replaced. You could check them into source control but you must ensure they can be written to at the end of a build. In VS the final output folder is specified in the normal VS project properties. It can be an expression using VS macros and/or hard coded path. BY default it is assumed to be the "\ConfigurationName" location mentioned above but can often be relative to where the solution (.sln) is located instead of where the Project (.vcxproj) file is located.


	WWW Facebook Twitter YouTube IP Logged

davidcoward Junior Member Offline Posts: 56 Joined: Oct 5^th, 2012	Re: Compile File Locations Reply #4 - Apr 19^th, 2018 at 12:26pm	Print Post
	Thanks, Tim! That works for me. David


	IP Logged

Pages: 1

‹ Previous Topic | Next Topic ›