Can I produce an ODB++ file with Eagle ?
On 8/24/2011 10:54 AM, Joe Adler wrote:
Hi Joe,
I'm afraid not. The ODB++ is a closed standard and requires an NDA to
use. Since we would likely implement the format using a ULP which is a
simple text file, i'm sure you could see why that wouldn't have worked
out so well.
The format could've been implemented internal to EAGLE, however the
developers decided not to support the format. You'd have to ask them why.
hth,
Jorge Garcia
Perhaps when Eagle changes over to the XML data format and its
description as mentioned in another topic, someone can NDA the format
and make a closed-source translator. Too bad an Ulp wouldn't be allowed
due to odb++ licensing. :/ If a similar someone could NDA the existing
binary Eagle data formats perhaps a similar closed-source translator
program could do that as well, but it sounds like life for such a
someone will be easier in a few months.
Jorge Garcia wrote:
>> Can I produce an ODB++ file with Eagle ?
>>
Hi Joe, I'm afraid not. The ODB++ is a closed standard and requires an NDA to use. Since we would likely implement the format using a ULP which is a simple text file, i'm sure you could see why that wouldn't have worked out so well. The format could've been implemented internal to EAGLE, however the developers decided not to support the format. You'd have to ask them why. hth,Jorge Garcia
