[Ipopt] IpOpt compiling problem in MSVC 10

Carlos Gomez carlos.gomez at autom.uva.es
Fri Jul 4 05:40:28 EDT 2014


Ok. With that change it worked. Thanks.
<http://3.bp.blogspot.com/-ke3pTHNJHiw/UKQZoce0FpI/AAAAAAAAAJc/wechAv8blAw/s1600/Imagen2.jpg> 

	*Piensa si es realmente necesario imprimir este correo. *
*Think before ink. *
*Pensez à l'environnement avant d'imprimer ce message. *

El 03/07/2014 19:12, Carlos Gomez escribió:
> Dear Stefan:
>     Thank you very much. I didn't see that thread. I can't try it 
> right now, but first thing tomorrow morning, so I can let you know.
>
> Best regards, Carlos Gómez Palacín.
> <http://3.bp.blogspot.com/-ke3pTHNJHiw/UKQZoce0FpI/AAAAAAAAAJc/wechAv8blAw/s1600/Imagen2.jpg> 
>
> 	*Piensa si es realmente necesario imprimir este correo. *
> *Think before ink. *
> *Pensez à l'environnement avant d'imprimer ce message. *
>
> El 03/07/2014 18:11, Stefan Vigerske escribió:
>> Hi,
>>
>> there is a fix for it, but it hasn't made it into a release yet:
>> https://projects.coin-or.org/Ipopt/changeset/2492/trunk
>> You essentially need to add src/Common/IpTaggedObject.cpp back into 
>> the list of files that need to be compiled.
>>
>> Stefan
>>
>> On 07/03/2014 11:29 AM, Carlos Gomez wrote:
>>> To whom it may concern:
>>>       I'm trying to compile the project provided in the sources, called
>>> IpOpt-vc10.sln using Microsoft Visual Studio 2010. But, when 
>>> generating the dll,
>>> a weird error is shown, it doesn't recognize the symbol unique_tag_.
>>>
>>> 1> IpAugRestoSystemSolver.obj : error LNK2001: extern symbol 
>>> "private: static
>>> unsigned int Ipopt::TaggedObject::unique_tag_"
>>> (?unique_tag_ at TaggedObject@Ipopt@@0IA) unsolved
>>>
>>> If I check the symbols (dumpbin \symbols + removing the  /GL) I can 
>>> see the
>>> symbol in the file IpAugRestoSystemSolver.obj
>>>
>>> C31 00000000 UNDEF  notype       External     |
>>> ?unique_tag_ at TaggedObject@Ipopt@@0IA (private: static unsigned int
>>> Ipopt::TaggedObject::unique_tag_)
>>>
>>> I'm quite sure the problem comes because there is one library not 
>>> linked, but
>>> I'm not sure which one. Has this problem happened before?
>>>
>>> On the other hand, when trying to compile using MinGW, when 
>>> configuring, the
>>> process gets stuck checking for Matlab executable extension (MEXSUFFIX)
>>>
>>> Thanks in advanced. Carlos Gómez Palacín.
>>> -- 
>>> <http://3.bp.blogspot.com/-ke3pTHNJHiw/UKQZoce0FpI/AAAAAAAAAJc/wechAv8blAw/s1600/Imagen2.jpg> 
>>>
>>>
>>>     *Piensa si es realmente necesario imprimir este correo. *
>>> *Think before ink. *
>>> *Pensez à l'environnement avant d'imprimer ce message. *
>>>
>>>
>>>
>>> _______________________________________________
>>> Ipopt mailing list
>>> Ipopt at list.coin-or.org
>>> http://list.coin-or.org/mailman/listinfo/ipopt
>>>
>>
>>
>> __________ Información de ESET NOD32 Antivirus, versión de la base de 
>> firmas de virus 10040 (20140703) __________
>>
>> ESET NOD32 Antivirus ha comprobado este mensaje.
>>
>> http://www.eset.com
>>
>>
>>
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.coin-or.org/pipermail/ipopt/attachments/20140704/9a8778a9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Imagen2.jpg
Type: image/jpeg
Size: 1962 bytes
Desc: not available
URL: <http://list.coin-or.org/pipermail/ipopt/attachments/20140704/9a8778a9/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1962 bytes
Desc: not available
URL: <http://list.coin-or.org/pipermail/ipopt/attachments/20140704/9a8778a9/attachment-0001.jpe>


More information about the Ipopt mailing list