[CMake] Proposal of Microsoft DLLs to Borland wrapping capabilities

[Luca Picello]

Yes I submitted but no answer received :-(
Nobody knows about next release of C++ Builder. I just know about Dephi 
studio integration but really nothing about compiler fixes.
Hope to see the light at the end of this tunnel...

thank you for your attention,
Luca



David Cole wrote:

> Have you posted any emails to Borland asking them to fix their 
> compiler to work with VTK/ITK? They could download the source 
> themselves and try building static/debug to improve their compiler... 
> I know VTK and ITK are large, but surely there are many C++ projects 
> out there in the world that are even larger. Does Borland only care 
> about small projects?
>
> And if Borland doesn't fix their compiler, why not give Visual Studio 
> and the Microsoft compiler a shot? Surely it's cheaper than all the 
> time and effort spent trying to get Borland to address these issues.
>
> All the great GUI building tools in the world aren't going to help you 
> make a decent piece of software if you can't link the libraries you 
> need for the non-GUI bits...
>
> 2 cents,
> David Cole
>
> Luca Picello wrote:
>
>> Hello Andy,
>> I'm using Borland C++ builder 6. Not the free compiler.
>> It seems old version (free) runs better than newer. ITK for example 
>> does not compile and is not supported for bcc6.
>> And VTK is now incredibly big too. More than maximum allowed by 
>> Borland limits especially compiling in debug mode or static linkage. 
>> [ http://www.itk.org/HTML/CompilerIssues.htm ]
>>
>> Converting to omf is enough only for pure C functions. For C++ we 
>> have different naming conventions.
>>
>> [from 
>> http://www.devarticles.com/index2.php?option=content&do_pdf=1&id=931&hide_js=1 
>> ]
>> there are differences in the schemes that different vendors adopt to 
>> mangle member names. The ANSI C++ standard does not govern the 
>> specifications of how a compiler should mangle class member names. 
>> Today, in absence of a strict standard in place, all the vendors have 
>> each developed their own techniques for name mangling, and the 
>> resulting conventions are certainly not compatible
>>
>> However my idea ( if applicable ) will result applicable only to dlls 
>> with release compilation option because different environments uses 
>> different intermediate/debug files. It could me my proposal could be 
>> completely useless but.. I'd like to hear your opinion.
>> Any comments?
>>
>> Luca
>>
>>
>>
>>
>>
>> Andy Cedilnik wrote:
>>
>>> Hi Luca,
>>>
>>> What exactly is the problem with VTK and Borland? We run nightly
>>> dashboard of VTK on borland with and without Tcl wrapping.
>>>
>>> That said, you could run a custom command that converts libraries to 
>>> omf
>>> format if that is what you want.
>>>
>>>       Andy
>>>
>>> Luca Picello wrote:
>>>
>>>  
>>>
>>>> I'd like to use Borland C++ builder IDE which is great for GUI
>>>> development with VTK/ITK etc.
>>>> However due to Borland compiler bugs it is impossible to successfully
>>>> compile VTK > 4.4.
>>>> I do not know when and if those bugs will be resolved but a possible
>>>> solution can be wrapping classes from DLLs from Microsoft compiler and
>>>> include them in the project.
>>>> This work is pretty hard due of impilib impdef etc tools that have to
>>>> be invoked and manual text files we have to produce to include every
>>>> single function from MS-DLLs.
>>>> Is there or there will be, any way to do it automatically with cmake?
>>>>
>>>> Thank you,
>>>> Luca
>>>>
>>>> _______________________________________________
>>>> CMake mailing list
>>>> CMake at cmake.org
>>>> http://www.cmake.org/mailman/listinfo/cmake
>>>>   
>>>
>>>
>>>
>>>
>>>  
>>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> CMake mailing list
>> CMake at cmake.org
>> http://www.cmake.org/mailman/listinfo/cmake
>>  
>>
>
> .
>