X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Subject: Re: [geda-user] gnetlist/xorn: can't generate netlist on PCB backend
To: geda-user AT delorie DOT com
References: <bd0f0ba8-fc65-d014-90f9-72412e45ab02 AT s5tehnika DOT net>
 <alpine DOT DEB DOT 2 DOT 21 DOT 2005261041020 DOT 1232 AT nimbus>
From: "Branko (brankob AT s5tehnika DOT net) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID: <cf6b5c66-c683-871a-e737-7c52bc6eaa09@s5tehnika.net>
Disposition-Notification-To: Branko <brankob AT s5tehnika DOT net>
Date: Tue, 26 May 2020 10:12:29 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.8.1
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.21.2005261041020.1232@nimbus>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: sl
Content-Transfer-Encoding: 8bit
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

Weird.

After rebooting my system, it started working again correctly AFAICT.
At least as PCB import. Didn't have the time to check manual methods yet.

Forget that I asked...




On 26. 05. 20 08:47, Roland Lutz wrote:
> Hi Branko,
> 
> On Tue, 26 May 2020, Branko (brankob AT s5tehnika DOT net) [via 
> geda-user AT delorie DOT com] wrote:
>> Recently I noticed trhat I can't for the life of me generate correct 
>> netlist from schematics either manually or as schematic import from PCB.
> 
> since gEDA/gaf version 1.10.0, a GUI message dialog is shown when 
> importing from PCB fails.  Do you see a message dialog, and if so, what 
> errors does it report?
> 
>> "gnetlist -v -g PCB  -o TEST4.pcb TEST4.sch" gives me output with this 
>> content ( minus starred demacartion lines):
>>
>> /*************/
>> unnamed_net2<-->R2-1 R1-1.
>> unnamed_net1<-->R2-2 R1-2.****
>> /*************/
>>
>>
>> Just those two lines. No some header and other fields, that one would 
>> expect in pcb file...
> 
> As far as I can tell, that's the correct output for the `PCB' backend. 
> This backend doesn't output a PCB file but a netlist in a format used to 
> import it to PCB.
> 
> As a side note, PCB's import functionality doesn't use the `PCB' backend 
> but PCB's own `pcbfwd' backend which produces a list of PCB commands to 
> execute.
> 
> Roland
>