On 1/30/2013 4:18 PM, Ryan Sturmer wrote:
I would be excited to do a cleaned up documentation of these formats.
Could I get a sense from any developers that are listening, where the
greatest need is? (Does it make more sense to start documenting the sch
library format, the schematic? the pcb fo
I would be excited to do a cleaned up documentation of these formats.
Could I get a sense from any developers that are listening, where the
greatest need is? (Does it make more sense to start documenting the sch
library format, the schematic? the pcb format? etc?)
-R
On Wed, Jan 30, 2013 at 3:
Le 30/01/2013 21:32, Dick Hollenbeck a écrit :
On 01/30/2013 01:58 PM, Pinault Nicolas wrote:
Hi,
There is a document describing Kicad file formats on bazaar. The last
revision is quite old (2011-12-04).
Is this document up to date ?
There are probably two questions to ask here:
1) Is this do
On 01/30/2013 01:58 PM, Pinault Nicolas wrote:
> Hi,
>
> There is a document describing Kicad file formats on bazaar. The last
> revision is quite old (2011-12-04).
> Is this document up to date ?
There are probably two questions to ask here:
1) Is this document in rev control the newest one ava
Hi,
There is a document describing Kicad file formats on bazaar. The last
revision is quite old (2011-12-04).
Is this document up to date ?
Best regards,
Nicolas
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developer
On 1/30/2013 4:33 AM, Brian Sidebotham wrote:
> Hi Wayne,
>
> You're right - it's not exactly straight forward, there are problems to
> solve.
>
> I got the specs file to work correctly with the variable substitution,
> perhaps you could try the spec90 file I attached to another mail on the
> lis
Hi,
though the fixes for #1101718 and #1102381 have already been committed,
I wasn't really satisfied with their solution. Find attached a cleaner
patch for both issues, more consistent with the existing code.
Best regards,
--
Jacobo Aragunde
Software Engineer at Igalia
=== modified file 'eesche
On 28 January 2013 20:00, Wayne Stambaugh wrote:
> I created a hard coded spec file from -dumpspec that
> defines -lmsvcr90 in the link option list and
> -D__MSVCRT_VERSION__=0x0900 in the compile option list. This seemed to
> work except now the linker is complaining:
>
>
> c:/mingw/bin/../lib/
The current source code repository for the MinGW runtime is at:
http://sourceforge.net/p/mingw/mingw-org-wsl/ci/21762bb4a1bd0c88c38eead03f59e8d994349e83/tree/
It has changed a lot since 3.20 and in fact rolls in win32api too. Both of
these will be released as one package and the next version to be
In fact I just looked, and yes - the last patch in his list sorts out
time...
Best Regards, Brian.
On 30 January 2013 09:33, Brian Sidebotham wrote:
> Hi Wayne,
>
> You're right - it's not exactly straight forward, there are problems to
> solve.
>
> I got the specs file to work correctly with t
Hi Wayne,
You're right - it's not exactly straight forward, there are problems to
solve.
I got the specs file to work correctly with the variable substitution,
perhaps you could try the spec90 file I attached to another mail on the
list? I'm using the latest MinGW version - 4.7.2 too.
I wonder i
11 matches
Mail list logo
