$Adam

In order to build for x64 with Visual Studio 2008, you must have the "Pro" version. - The free "Express" version will not work. Instructions on using the "Express" version of newer renditions of Visual Studio are forthcoming.

I was wondering whether there was an estimated date when these instructions would forthcome. Also, I'm wondering whether it would be possible to create x64 externals with older versions of Windows and VS? I'm building my externals for Windows on an emulated Windows XP SP3 partition with VS Express 2010 and since I'm only using that partition to build my (free) library, I don't really want to invest on a newer version of the OS and/or a paid version of Visual Studio.

max-64-bit-and-visual-studio

Thanks for pointing this out, Ádám. It looks like this page needs a bit of editing, and it just missed the 6.1.3 SDK update ( now available @ 

https://cycling74.com/download/MaxSDK-6.1.3.zip

VS2010 Express is capable of producing an x64 binary. Any of the example projects should provide this. My personal recommendation is to follow the same instructions provided for updating a VS2008 project, which is to just make a new project.

I know that's not the most satisfying work to do, but it minimizes the problems caused by old cruft left in the project files.

Thanks for pointing this out, Ádám.  It looks like this page needs a bit of editing, and it just missed the 6.1.3 SDK update ( now available @ https://cycling74.com/download/MaxSDK-6.1.3.zip ).

VS2010 Express is capable of producing an x64 binary.  Any of the example projects should provide this.  My personal recommendation is to follow the same instructions provided for updating a VS2008 project, which is to just make a new project.

I have a question, though, as I'm quite unfamiliar with VS. In my project, I have a single 

 file containing all the 30+ externals (as separate 

 file for properties. I remember spending a considerable amount of time with creating this setup, I had to edit the files with text editors (as the VS editor seemed to introduce some weird things), and, worst of all, I can't remember how I did it. My purpose is to keep having a single 

 file, which would contain the externals, and an option to switch between Max 5 and Max 6 building (in XCode, I also have a single project file with separate targets for each external and I can switch between Max 5 and Max 6 by switching to different build configurations).

In your personal opinion, would it still make sense to re-create this whole structure based on the new 

 files provided by the new SDK, or does it make more sense in this particular scenario to try to update manually my old project files?

I have a question, though, as I'm quite unfamiliar with VS. In my project, I have a single sln file containing all the 30+ externals (as separate vcxproj files) and a common props file for properties. I remember spending a considerable amount of time with creating this setup, I had to edit the files with text editors (as the VS editor seemed to introduce some weird things), and, worst of all, I can't remember how I did it. My purpose is to keep having a single sln file, which would contain the externals, and an option to switch between Max 5 and Max 6 building (in XCode, I also have a single project file with separate targets for each external and I can switch between Max 5 and Max 6 by switching to different build configurations).

In your personal opinion, would it still make sense to re-create this whole structure based on the new vcxproj and props files provided by the new SDK, or does it make more sense in this particular scenario to try to update manually my old project files?

My "native" platform is the Mac and so I too find some aspects of VS a bit bewildering. I have also experienced that it is sometimes more predictable to edit the files in a text editor.

 it won't have to be updated at all (you 

 files). I say "probably" because its impossible say universally that it will be okay.

As of the Max 6.1 SDK we are using props files for our projects. Perhaps this will help in figuring out how to update your 

 files because ours already have similar references in them.

Unfortunately, I can't provide a silver bullet, but hopefully it won't be as painful as creating those files in the first place!

My "native" platform is the Mac and so I too find some aspects of VS a bit bewildering.  I have also experienced that it is sometimes more predictable to edit the files in a text editor.

Making a sln from a bunch of vcxproj files is pretty easy probably it won't have to be updated at all (you probably just need to update the vcxproj files).  I say "probably" because its impossible say universally that it will be okay.

As of the Max 6.1 SDK we are using props files for our projects.  Perhaps this will help in figuring out how to update your vcxproj files because ours already have similar references in them.

Unfortunately, I can't provide a silver bullet, but hopefully it won't be as painful as creating those files in the first place!


Max 64 bit and Visual Studio