Can you please help me with the information regarding differences between 2011b and 2016b?

I wanted to understand differences between 2011b and 2016b from libraries and codegen point of view?Also if there are any changes in the .p files between the two versions?If yes, what files and what kind of changes?

Answer 1

[Walter Roberson]

If I recall correctly, it is necessary to rebuild .p files somewhere between those two releases. The internal working of .p files is not documented so all we can say is it won't work.

I would expect that somewhere along the way the .p files became 64 bit aware.

There have been a number of changes to the internal interfaces between those two releases. The changes are mostly undocumented, other than the changes for 64 bit compatibility.

Officially, .mexw32 and .mexw64 files are only compatible with the MATLAB release they were compiled by. In practice they tend to be usable for several years, but eventually they need to be recompiled from source.

If your code uses graphics then it would definitely need to be recompiled starting with R2014b because of big changes to the graphics system.

[shashank mall]

Thanks a lot Walter for your response. The thing is I am currently using 2011b for modeling and autocodegen(RTW) purposes. We are now planning to migrate to 2016b for the same. I wanted to understand differences between 2011b and 2016b from libraries and codegen point of view?Also if there are any changes in the .p files between the two versions? Long back(2007 Matlab version) our client worked with MathWorks and came up with few customized .p files for codegen. These changes worked fine with 2011b but now since we are migrating to 2016b, I am not sure if its still going to work.

[Steven Lord]

According to the Release Notes for MATLAB, starting in release R2015b if you're trying to run P-coded files generated with release R2007a or earlier you will need to rebuild them.

Shashank, to answer your general question about what changed between those releases I recommend that you read or at least skim the Release Notes for the products you use. [Some products may have been combined or renamed; if you don't see a product you used in the older release search the documentation for that product name and the word "rename" and you should see the new name.]

[Walter Roberson]

If the .p files do graphics then you will probably have difficulty. If they only do computation, they might possibly still work.

I suspect that if the .m source is available for the .p files then it would be a good idea to re-do the pcode, as the interpreter and Just In Time engine have improved.

I gather that the workflow for building projects has changed, especially with respect to configuring toolchains. I have not done any RTW work.

If you are using device drivers then you would need to worry about 32 bit vs 64 bit. If you are using Instrument Control Toolbox then there might be differences that originate in "Legacy" vs "Session Based", and many fewer devices are supported now.