#1 Burning Software

Is linked to the dynamic Microsoft CRT runtime - do you have the steps to configure it to link to the static libraries?

Cheers,

Stuart

Not sure about what problem you have. Just add StarBurn.lib to the library path and that should be enough...

Thanks for the reply, but perhaps you misunderstood my question.

The StarBurn.lib appears to be statically linking to the Microsoft runtime DLLs. I can build with the static StarBurn.lib just fine, but I cannot distribute my DLL without distributing the MSVCR71.dll and MSVCP71.dll.

I cannot build with the /MT option or I get a series of __imp__* linker errors.

Cheers,

Stu

There are TWO versions of StarBurn.lib. One for dynamic linking (thru the StarBurn.dll) and one for just static linking. Please check our samples - they do not need anything except msvcrt.dll (it's already included into all of the MS OSes distribution). Please check you're using correct .lib file.

Yes - I understand this. I have linked to the static StarBurn library. You have confirmed for me what I was asking. Starburn requires the MSVCRT runtime DLL - you do not build a version of the StarBurn.lib that statically links to the Microsoft runtime. Is it MSVCR71.dll? This is not necessarily available on all OSs - we ran into this very problem.

Cheers,

Stuart

Yes, StarBurn requires dynamic MS tun-time (just b/s half of MS own libraries don't work when built as pure static). If you'll check our samples with dumpbin.exe or somethink like it you'll see they import code only from MSVCRTL.DLL which is available everywhere. If you're using some compiles with own dynamic run-time you'll have to either redistribute this run-time with your application or contact your compiler vendor asking them to enable DEFAULT OS RTL. We do no control your build process.

...and if it's a real big problem for you (you cannot redistribute your compiler RTL and your compiler vendor cannot switch you to default system RTL) please drop us a line and we'll try to find out a workaround for you.

Hello , this library is a very good burning engine implementations, i've searched and tested some libs but none was that powerful ,i think you are the one and only, congratulations

i have a question , how can i use the static lib in Borland C++ Builder ?

thanks, have a nice day....


sorry about my bad English ,i'am not from around here

Unfortunately we do not provide static libraries for Borland C++ Builder. And even if you'll manage to link statically to LIBs we have you'll hit RTL compatibility problems. That's why we do not recommend using LIBs and static linking and kindly ask users to stick with DLL (dynamic linking) or even OCX if possible.

Thanks for clearing, sticking with the DLL it's fine for me....

Good!