Re: [Gerbv-devel] Export-to-Gerber code has been started

[Dan M. <da...@mc...>]

Stuart Brorson wrote:
> Julian --
> 
>>    I've started adding the code to export a loaded file back to a
>> RS-274X file.  It still needs a lot of work, but it seems to export
>> PCB-exported files well even at this early stage.  I need to do some
>> tweaking to the gerb_image struct in order to continue work on it
>> though, so I thought I would wait until we got 2.0.1 out before I
>> changed anything non-trivial.  For now, the exporting stuff is just
>> accessible through the command line (--export=rs274x) if you want to try
>> it out.
> 
> This is a very nice feature.  I just spent three minutes playing with
> it.
> 
> It worked great on some of my boards generated using gEDA/PCB.  It's
> very, very speedy when used in command-line mode
> 
> I also looked at the Eaglecad board in the examples dir.  If I do
> this:
> 
> 1.  gerbv -x rs274x -o foo.gbr top-cop.gbx
> 2.  gerbv foo.gbr
> 
> Then gerbv complains a lot about some (but not all) apertures as
> undefined.  Example:
> 
> Aperture [14] is not defined
> Aperture [14] is not defined
> Aperture [15] is not defined
> Aperture [15] is not defined
> 
> I will try some other files later by taking them on a round trip --
> first reading the old file, exporting it, and then looking at the
> newly generated gerber.

if you feel really motivated, then you can export the original, and the 
resaved gerber to png files and then compare them for differences via 
software.  Perhaps I should extend the testsuite to do that 
automatically.  Most of the framework is there.

-Dan