# VisualStudio 2015 Exporter

**URL:** <https://forum.juce.com/t/visualstudio-2015-exporter/23769>\
**Category:** The Projucer\
**Created:** [August 16, 2017, 1:27pm UTC](https://forum.juce.com/t/visualstudio-2015-exporter/23769 "2017-08-16T13:27:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![wkundrus](https://avatars.discourse-cdn.com/v4/letter/w/34f0e0/32.png) [@wkundrus](https://forum.juce.com/u/wkundrus)\
**Post date:** [August 16, 2017, 1:27pm UTC](https://forum.juce.com/t/visualstudio-2015-exporter/23769/1 "2017-08-16T13:27:12Z")

</div>

I would like to specify the instruction set and I would like to set a Precompiled Header File. Both is not possible, it seems. The way you can customise the project for MacOS does not work on Windows. If I add /arch:SSE2 in the additional compiler options, VS ignores them and gives a warning.

I am more and more under the impression, that Projucer should rather use Cmake technology, rather then trying to come up with a competing system to generate project files.

---

<div class="post-metadata">

**Author:** ![xenakios](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/xenakios/32/4047_2.png) [@xenakios](https://forum.juce.com/u/xenakios)\
**Post date:** [August 16, 2017, 1:33pm UTC](https://forum.juce.com/t/visualstudio-2015-exporter/23769/2 "2017-08-16T13:33:56Z")

</div>

Are you building as 64 bit? The SSE2 flag is redundant in that case.

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [August 16, 2017, 1:43pm UTC](https://forum.juce.com/t/visualstudio-2015-exporter/23769/3 "2017-08-16T13:43:49Z")

</div>

If the projucer supported cmake, it wouldn’t make it any easier for us to add the features you’re asking for. In fact it’d be harder, as we’d have one more target platform that would need to have these things added.

If you really want micro-control of your build, and if you like cmake, then why not just use it? The projucer’s not compulsory, many juce users have their own custom build setups.

---

<div class="post-metadata">

**Author:** ![wkundrus](https://avatars.discourse-cdn.com/v4/letter/w/34f0e0/32.png) [@wkundrus](https://forum.juce.com/u/wkundrus)\
**Post date:** [August 16, 2017, 1:55pm UTC](https://forum.juce.com/t/visualstudio-2015-exporter/23769/4 "2017-08-16T13:55:26Z")

</div>

I like the support for so many plugin/app formats. That’s why I want to stay with it for now.

---

<div class="post-metadata">

**Author:** ![mcmartin](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/mcmartin/32/7432_2.png) [@mcmartin](https://forum.juce.com/u/mcmartin)\
**Post date:** [August 16, 2017, 2:04pm UTC](https://forum.juce.com/t/visualstudio-2015-exporter/23769/5 "2017-08-16T14:04:23Z")

</div>

`<self-promo mode>`

If you want to use CMake to build your JUCE projects, you can have a look at [https://github.com/McMartin/JUCE.cmake](https://github.com/McMartin/JUCE.cmake).

`</self-promo mode>`