Originally posted by: TheLoneStranger

Hello,

In relation to the problems with _ITERATOR_DEBUG_LEVEL, I can see 2 unanswered questions for the debug builds...

https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014579684&ps=25

https://www.ibm.com/developerworks/community/forums/html/topic?id=6fef796d-68ba-4024-baf9-341693eff1a8

I have just finished a proof-of-concept using OPL and I must say it was quite painful doing so without debug information.

1. Are there any plans to do a new release/patch with the debug builds?

2. Do you have a work-around that does not involve rebuilding every child library for my project (I cannot as I do not own all the libraries)

I understand that there are a significant number of libraries that you would need to compile in debug mode. However, without having a debug build, I am very reluctant to proceed further with OPL.

Regards,

TLS

Originally posted by: TheLoneStranger

Update..

A few people have emailed me personally to suggest that I can convert the MOD to an LP file and progress from there.

I am great grateful to them for the help. However, this is not an ideal solution work-around.

There are 2 issues here.

1. My clients will be delivering the files in .MOD format. 

2. I already have a significant amount of code that uses the IloOpl... classes. Rewriting the code to use concert/cplex is possible, but another added problem.

TLS

Originally posted by: VincentBeraudier

We are currently investigating the builds of OPL with /MDd option with the aim of a delivery in a next release.