gerbv-devel Mailing List for gerbv — a Gerber (RS-274X) viewer (Page 3)
Brought to you by:
spetm,
thepurlieu
You can subscribe to this list here.
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(249) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2008 |
Jan
(263) |
Feb
(32) |
Mar
(48) |
Apr
(45) |
May
(46) |
Jun
(37) |
Jul
(6) |
Aug
(279) |
Sep
(86) |
Oct
(22) |
Nov
(13) |
Dec
(8) |
2009 |
Jan
(29) |
Feb
(40) |
Mar
(55) |
Apr
(10) |
May
|
Jun
(8) |
Jul
(33) |
Aug
(30) |
Sep
(8) |
Oct
(15) |
Nov
(20) |
Dec
(7) |
2010 |
Jan
(6) |
Feb
(39) |
Mar
(11) |
Apr
(15) |
May
(7) |
Jun
(19) |
Jul
(5) |
Aug
(25) |
Sep
(8) |
Oct
|
Nov
(16) |
Dec
(13) |
2011 |
Jan
(30) |
Feb
(15) |
Mar
(55) |
Apr
(32) |
May
(11) |
Jun
(3) |
Jul
(2) |
Aug
(11) |
Sep
(9) |
Oct
(4) |
Nov
(11) |
Dec
(6) |
2012 |
Jan
(6) |
Feb
(3) |
Mar
(24) |
Apr
(3) |
May
(5) |
Jun
(8) |
Jul
(5) |
Aug
(3) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
2013 |
Jan
(4) |
Feb
(1) |
Mar
(2) |
Apr
(6) |
May
(13) |
Jun
(9) |
Jul
(4) |
Aug
|
Sep
(4) |
Oct
(1) |
Nov
(4) |
Dec
(32) |
2014 |
Jan
(3) |
Feb
(2) |
Mar
(2) |
Apr
|
May
(2) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(23) |
Nov
(9) |
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
(3) |
Nov
|
Dec
(2) |
2016 |
Jan
(10) |
Feb
(7) |
Mar
(6) |
Apr
|
May
(5) |
Jun
(1) |
Jul
(8) |
Aug
(2) |
Sep
(4) |
Oct
(28) |
Nov
(6) |
Dec
|
2017 |
Jan
|
Feb
(42) |
Mar
(9) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
(16) |
Jun
(8) |
Jul
(5) |
Aug
(2) |
Sep
(9) |
Oct
(1) |
Nov
(8) |
Dec
(1) |
2019 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
(8) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(4) |
2021 |
Jan
(6) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(8) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
From: Sergey A. <aly...@gm...> - 2018-09-03 14:26:35
|
On Mon, Sep 3, 2018 at 4:05 PM Patrick Franken <p.f...@ai...> wrote: > > Done! Patch is attached to this email. > > BTW, how do I apply as a member of this mailinglist? Kinda annoying to get the approval mails all the time. You can subscribe here: https://sourceforge.net/projects/gerbv/lists/gerbv-devel |
From: Patrick F. <p.f...@ai...> - 2018-09-03 12:12:41
|
Done! Patch is attached to this email. BTW, how do I apply as a member of this mailinglist? Kinda annoying to get the approval mails all the time. On Mon, 3 Sep 2018 at 11:41 Sergey Alyoshin <aly...@gm...> wrote: > On Mon, Sep 3, 2018 at 2:22 PM Patrick Franken <p.f...@ai...> > wrote: > > > > Just solved the issue. It was caused by the order of the GCC arguments, > see > https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition#How_to_Fix_a_Problem > for more details. > > gcc -Wall -g example_1.c -o test `pkg-config --cflags libgerbv` > `pkg-config --libs libgerbv` > > works like a charm > > > > Does it make sense to update the examples accordingly? I could take care > of it. > > Yes, please. > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Gerbv-devel mailing list > Ger...@li... > https://lists.sourceforge.net/lists/listinfo/gerbv-devel > |
From: Sergey A. <aly...@gm...> - 2018-09-03 11:41:19
|
On Mon, Sep 3, 2018 at 2:22 PM Patrick Franken <p.f...@ai...> wrote: > > Just solved the issue. It was caused by the order of the GCC arguments, see https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition#How_to_Fix_a_Problem for more details. > gcc -Wall -g example_1.c -o test `pkg-config --cflags libgerbv` `pkg-config --libs libgerbv` > works like a charm > > Does it make sense to update the examples accordingly? I could take care of it. Yes, please. |
From: Patrick F. <p.f...@ai...> - 2018-09-03 09:50:04
|
Just solved the issue. It was caused by the order of the GCC arguments, see https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition#How_to_Fix_a_Problem for more details. gcc -Wall -g example_1.c -o test `pkg-config --cflags libgerbv` `pkg-config --libs libgerbv` works like a charm Does it make sense to update the examples accordingly? I could take care of it. Patrick On Mon, 3 Sep 2018 at 06:21 Patrick Franken <p.f...@ai...> wrote: > GCC compiles with > -L/usr/local/lib -lgerbv -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 > -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 > -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype > > ls /usr/local/lib > -rw-r--r-- 1 root root 1372794 Sep 2 23:18 libgerbv.a > -rwxr-xr-x 1 root root 1161 Sep 2 23:18 libgerbv.la > lrwxrwxrwx 1 root root 17 Sep 2 23:18 libgerbv.so -> > libgerbv.so.1.0.7 > lrwxrwxrwx 1 root root 17 Sep 2 23:18 libgerbv.so.1 -> > libgerbv.so.1.0.7 > -rwxr-xr-x 1 root root 719408 Sep 2 23:18 libgerbv.so.1.0.7 > > Looks pretty reasonable to me. Gerbv was compiled from the current master > HEAD with ElectricFence support. > > On Mon, 3 Sep 2018 at 05:55 Joerg Wunsch <j...@ur...> wrote: > >> As Patrick Franken wrote: >> >> > /home/patrick/example_1.c:7: undefined reference to `gerbv_create_image' >> > /home/patrick/example_1.c:30: undefined reference to >> `gerbv_destroy_image' >> >> Sure you are linking against the correct version of the gerbv library? >> Can you post the linker commandline? It might also help to include a >> "-v" option to the linker, so it's telling you about the paths it uses. >> -- >> cheers, Joerg .-.-. --... ...-- -.. . DL8DTL >> >> http://www.sax.de/~joerg/ >> Never trust an operating system you don't have sources for. ;-) >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Gerbv-devel mailing list >> Ger...@li... >> https://lists.sourceforge.net/lists/listinfo/gerbv-devel >> > |
From: Patrick F. <p.f...@ai...> - 2018-09-03 06:22:09
|
GCC compiles with -L/usr/local/lib -lgerbv -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype ls /usr/local/lib -rw-r--r-- 1 root root 1372794 Sep 2 23:18 libgerbv.a -rwxr-xr-x 1 root root 1161 Sep 2 23:18 libgerbv.la lrwxrwxrwx 1 root root 17 Sep 2 23:18 libgerbv.so -> libgerbv.so.1.0.7 lrwxrwxrwx 1 root root 17 Sep 2 23:18 libgerbv.so.1 -> libgerbv.so.1.0.7 -rwxr-xr-x 1 root root 719408 Sep 2 23:18 libgerbv.so.1.0.7 Looks pretty reasonable to me. Gerbv was compiled from the current master HEAD with ElectricFence support. On Mon, 3 Sep 2018 at 05:55 Joerg Wunsch <j...@ur...> wrote: > As Patrick Franken wrote: > > > /home/patrick/example_1.c:7: undefined reference to `gerbv_create_image' > > /home/patrick/example_1.c:30: undefined reference to > `gerbv_destroy_image' > > Sure you are linking against the correct version of the gerbv library? > Can you post the linker commandline? It might also help to include a > "-v" option to the linker, so it's telling you about the paths it uses. > -- > cheers, Joerg .-.-. --... ...-- -.. . DL8DTL > > http://www.sax.de/~joerg/ > Never trust an operating system you don't have sources for. ;-) > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Gerbv-devel mailing list > Ger...@li... > https://lists.sourceforge.net/lists/listinfo/gerbv-devel > |
From: Joerg W. <j...@ur...> - 2018-09-03 05:55:20
|
As Patrick Franken wrote: > /home/patrick/example_1.c:7: undefined reference to `gerbv_create_image' > /home/patrick/example_1.c:30: undefined reference to `gerbv_destroy_image' Sure you are linking against the correct version of the gerbv library? Can you post the linker commandline? It might also help to include a "-v" option to the linker, so it's telling you about the paths it uses. -- cheers, Joerg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) |
From: Patrick F. <p.f...@ai...> - 2018-09-02 22:57:29
|
Dear gerbv folks, while compiling the libgerbv examples I get the following error from GCC /tmp/ccz2ddI2.o: In function `main': /home/patrick/example_1.c:7: undefined reference to `gerbv_create_image' /home/patrick/example_1.c:10: undefined reference to `gerbv_image_create_line_object' /home/patrick/example_1.c:11: undefined reference to `gerbv_image_create_line_object' /home/patrick/example_1.c:12: undefined reference to `gerbv_image_create_line_object' /home/patrick/example_1.c:15: undefined reference to `gerbv_image_create_arc_object' /home/patrick/example_1.c:16: undefined reference to `gerbv_image_create_arc_object' /home/patrick/example_1.c:19: undefined reference to `gerbv_image_create_arc_object' /home/patrick/example_1.c:22: undefined reference to `gerbv_image_create_arc_object' /home/patrick/example_1.c:25: undefined reference to `gerbv_image_create_rectangle_object' /home/patrick/example_1.c:26: undefined reference to `gerbv_image_create_rectangle_object' /home/patrick/example_1.c:30: undefined reference to `gerbv_destroy_image' collect2: error: ld returned 1 exit status GCC include and library parameters are properly set. /usr/local/lib and /usr/local/include both include the header file and library. Does anyone of you know what the reason could be? Any help appreciated. Thanks, Patrick |
From: Milton N. <mil...@bi...> - 2018-08-19 10:06:02
|
Hi all A couple of years ago I came across the Gerbv project on Sourceforge. Recently I have been working on a project to "port" the Gerbv library to C# (.Net managed platform), mostly for no other reason but "to see if I can". I've reach the stage where I can open and display Gerber and Drill files, of course the project requires a lot more work to become a fully functional Viewer. Still, I would like to put it out there in the open source world and hopefully attract other .Net developers to help with development of GerberVS (my project) to add functionality and performance. As my C# library code follows closely resembles the "structure" of Gerbv library, I would like to run this by the developers, in hope that you do not object to me posting my project "GerberVS" on Sourceforge to share it with other .Net developers. Naturally where appropriate I will give credits to the Gerbv developers. Thanks in advance. Milton Neal |
From: Sergey A. <aly...@gm...> - 2018-08-10 12:41:39
|
The following could be done with with something like: for i in `ldd $dirInstall/bin/gerbv.exe | grep mingw | cut -d' ' -f3`; do cp $i $dirInstall/bin/`basename $i` done On Wed, Mar 1, 2017 at 5:24 PM, Valerio Messina <ef...@io...> wrote: > cp $dirSys/mingw$bit/bin/libwinpthread-1.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libcairo-2.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libfontconfig-1.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libexpat-1.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libfreetype-6.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libbz2-1.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libharfbuzz-0.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libglib-2.0-0.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libintl-8.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libiconv-2.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libpcre-1.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libgraphite2.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libstdc++-6.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libpng16-16.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/zlib1.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libpixman-1-0.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libgdk-win32-2.0-0.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libgdk_pixbuf-2.0-0.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libgio-2.0-0.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libgmodule-2.0-0.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libgobject-2.0-0.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libffi-6.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libpango-1.0-0.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libpangocairo-1.0-0.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libpangoft2-1.0-0.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libpangowin32-1.0-0.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libgtk-win32-2.0-0.dll $dirInstall/bin > cp $dirSys/mingw$bit/bin/libatk-1.0-0.dll $dirInstall/bin |
From: Valerio M. <ef...@io...> - 2018-07-31 07:37:44
|
On 07/28/18 17:40, Sergey Alyoshin wrote: > Try this patch. OK worked. So release 2.6.2 with this patch compile well on Windows. I think the patch should be integrated in the release. Here my binaries: 32bit https://drive.google.com/open?id=1qts1sQ3XSheEtyH3ppE5FAE6-FwK4AAy 64bit https://drive.google.com/open?id=1dk2JZzbsQQe949PjXYIYd5tBp3Ww59yZ thank you, Valerio |
From: Sergey A. <aly...@gm...> - 2018-07-28 15:40:20
|
On Thu, Jul 26, 2018 at 4:49 PM, Valerio Messina via Gerbv-devel <ger...@li...> wrote: > hi, > I just tried to build the gerbv-2.6.2.tar.gz release sources: > https://sourceforge.net/projects/gerbv/files/gerbv/gerbv-2.6.2/ > on MSYS2/Win both 64 and 32 bit. > > In make stage, it complaint about: > pick-and-place.c:182: undefined reference to `screen' > Below see the complete errors. > How can be fixed? Try this patch. |
From: Valerio M. <ef...@io...> - 2018-07-26 14:03:08
|
hi, I just tried to build the gerbv-2.6.2.tar.gz release sources: https://sourceforge.net/projects/gerbv/files/gerbv/gerbv-2.6.2/ on MSYS2/Win both 64 and 32 bit. In make stage, it complaint about: pick-and-place.c:182: undefined reference to `screen' Below see the complete errors. How can be fixed? Instead works well with current git sources, both 64 and 32 bit: https://drive.google.com/open?id=1Wephu5ynPLcHKiKvuqkx3GwAqe1qflIY https://drive.google.com/open?id=1MSIdxeHmQqssFbtwXe5Xh-aHLkd5LqhW thank you, Valerio MINGW64: $ make ... libtool: link: gcc -shared .libs/amacro.o .libs/tooltable.o .libs/draw.o .libs/draw-gdk.o .libs/drill.o .libs/exportimage.o .libs/gerb_file.o .libs/gerb_image.o .libs/gerber.o .libs/gerbv.o .libs/pick-and-place.o .libs/csv.o .libs/gerb_stats.o .libs/drill_stats.o .libs/export-rs274x.o .libs/export-drill.o -LD:/ProgramFiles/msys64/mingw64/lib -lgtk-win32-2.0 -lgdk-win32-2.0 -lgdi32 -limm32 -lshell32 -lole32 -lpangowin32-1.0 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lintl -lcairo -g -O2 -mms-bitfields -mwindows -mms-bitfields -pthread -mms-bitfields -mms-bitfields -Wl,-luuid -pthread -o .libs/libgerbv-1.dll -Wl,--enable-auto-image-base -Xlinker --out-implib -Xlinker .libs/libgerbv.dll.a D:/ProgramFiles/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/7.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe: .libs/pick-and-place.o:pick-and-place.c:(.rdata$.refptr.screen[.refptr.screen]+0x0): undefined reference to `screen' collect2.exe: error: ld returned 1 exit status make[2]: *** [Makefile:561: libgerbv.la] Error 1 make[2]: uscita dalla directory "/d/AMBIENTE/Documents/c/gerbv-2.6.2/src" make[1]: *** [Makefile:472: all-recursive] Error 1 make[1]: uscita dalla directory "/d/AMBIENTE/Documents/c/gerbv-2.6.2" make: *** [Makefile:402: all] Error 2 MINGW32: $ make ... libtool: link: gcc -shared .libs/amacro.o .libs/tooltable.o .libs/draw.o .libs/draw-gdk.o .libs/drill.o .libs/exportimage.o .libs/gerb_file.o .libs/gerb_image.o .libs/gerber.o .libs/gerbv.o .libs/pick-and-place.o .libs/csv.o .libs/gerb_stats.o .libs/drill_stats.o .libs/export-rs274x.o .libs/export-drill.o -LD:/ProgramFiles/msys64/mingw32/lib -lgtk-win32-2.0 -lgdk-win32-2.0 -lgdi32 -limm32 -lshell32 -lole32 -lpangowin32-1.0 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lintl -lcairo -g -O2 -mms-bitfields -mwindows -mms-bitfields -pthread -mms-bitfields -mms-bitfields -Wl,-luuid -pthread -o .libs/libgerbv-1.dll -Wl,--enable-auto-image-base -Xlinker --out-implib -Xlinker .libs/libgerbv.dll.a D:/ProgramFiles/msys64/mingw32/bin/../lib/gcc/i686-w64-mingw32/7.3.0/../../../../i686-w64-mingw32/bin/ld.exe: .libs/pick-and-place.o: in function `pick_and_place_get_float_unit': D:\AMBIENTE\Documents\c\gerbv-2.6.2\src/pick-and-place.c:182: undefined reference to `screen' collect2.exe: error: ld returned 1 exit status make[2]: *** [Makefile:561: libgerbv.la] Error 1 make[2]: uscita dalla directory "/d/AMBIENTE/Documents/c/gerbv-2.6.2/src" make[1]: *** [Makefile:472: all-recursive] Error 1 make[1]: uscita dalla directory "/d/AMBIENTE/Documents/c/gerbv-2.6.2" make: *** [Makefile:402: all] Error 2 |
From: Sergey A. <aly...@gm...> - 2018-07-12 21:03:22
|
On Thu, Jul 12, 2018 at 2:23 PM, Sergey Alyoshin <aly...@gm...> wrote: > On Thu, Jun 14, 2018 at 12:37 AM, Miklos Marton > <mar...@gm...> wrote: >>> I have added "Load all" functionality for drop files. >>> But I want to show all file names to be loaded on "Load all", and this >>> is not yet ready. >> >> >> What do you mean under the "Load all" functionality?The merging of the open >> project and open gerber files? > > Present user with a list of all filenames to be opened, so he can > choose from it. > > >> Which branch did you added it? > > Sorry for long delay, it was not ready, but now it is. I will crate a > branch when I get to the computer. As for now I have commit access problem with git://git.geda-project.org/gerbv the repository is here: https://github.com/alyoshin/gerbv_file-drop |
From: Sergey A. <aly...@gm...> - 2018-07-12 11:23:18
|
On Thu, Jun 14, 2018 at 12:37 AM, Miklos Marton <mar...@gm...> wrote: >> I have added "Load all" functionality for drop files. >> But I want to show all file names to be loaded on "Load all", and this >> is not yet ready. > > > What do you mean under the "Load all" functionality?The merging of the open > project and open gerber files? Present user with a list of all filenames to be opened, so he can choose from it. > Which branch did you added it? Sorry for long delay, it was not ready, but now it is. I will crate a branch when I get to the computer. |
From: Miklos M. <mar...@gm...> - 2018-06-13 21:37:43
|
> I have added "Load all" functionality for drop files. > But I want to show all file names to be loaded on "Load all", and this > is not yet ready. What do you mean under the "Load all" functionality?The merging of the open project and open gerber files? Which branch did you added it? -- Best regards, Miklos Marton |
From: Miklos M. <mar...@gm...> - 2018-06-02 15:23:10
|
> From what I know detecting Gerber files based on their filename is a > total pain. There are some libraries such as > https://github.com/tracespace/whats-that-gerber/blob/master/index.jsaround > which work in some cases. But in most cases it is just disappointing > to the user. Thanks for sharing the link to the library! Well in my opinion implementing any kind of automated layer sorting would be an user experience improvement. > As mentioned before is this his issue already addressed by the Gerber > X2 extensions. We recommend our users to use these which works out > pretty well. > In my opinion we should >only< support X2 extensions as it is the only > solution which gives a fulfilling user experience. And it is a good > way to increase popularity of Gerber X2. I agree that X2 is the way to go, but the old fashioned RS-274 with their layer extensions/file name pattern will live for a while . At the another hand I would rather create a more simple layer sorting implementation first (based on extensions&filename patterns) for creating the infrastructure and then later we can work on upstreaming the X2 patch properly. After we got X2 support upstreamed it will be trivial to do the sorting based on the attributes. -- Best regards, Miklos Marton |
From: Valerio M. <ef...@io...> - 2018-06-01 14:56:20
|
On 05/31/18 23:16, Linda Huxley wrote: > I use KiCAD. I just looked into some Gerbers generated by KiCAD and > there doesn't appear to be any kind of comment or attribute in any of > the files that would betray the actual layer. (KiCAD is under heavy > development, so things may have changed in recent versions.) I just checked Gerber generated with 4.0.2 dated 2016-02-28, first line contain the attribute: TF.FileFunction,Profile,NP* for Edge.Cuts.gbr TF.FileFunction,Other,Fab,Top* for F.Fab.gbr TF.FileFunction,Soldermask,Top* for F.Mask.gbr TF.FileFunction,Legend,Top* for F.SilkS.gbr TF.FileFunction,Copper,L1,Top,Signal* for F.Cu.gbr TF.FileFunction,Copper,L2,Bot,Signal* for B.Cu.gbr TF.FileFunction,Soldermask,Bot* for B.Mask.gbr on a two layers PCB. Checked also 4.0.7 do the same. So this appear as X2 compliant, at least for layers (last X2 include the net-list too for post production checks). Valerio |
From: Valerio M. <ef...@io...> - 2018-06-01 14:27:19
|
On 05/31/18 23:16, Linda Huxley wrote: > I use KiCAD. I just looked into some Gerbers generated by KiCAD and > there doesn't appear to be any kind of comment or attribute in any of > the files that would betray the actual layer. (KiCAD is under heavy > development, so things may have changed in recent versions.) Wikipedia declare KiCAD 4.0.7 as Gerber X2 compliant: https://en.wikipedia.org/wiki/Comparison_of_EDA_software need a correction? > KiCAD insists on writing out Gerbers with a file name suffix that > indicates the layer. However, my board house insists that all of the > file names be the same, and that the file extension specify the layer. Gerber specification [1] clearly say that all layer files must have .gbr extension. Layer should be in the name or better in an attribute for X2. So KiCAD is compliant, while manufacturer isn't (anyway i saw many asking out of standard like this) [1] section.3.2 pag.37 section 6.2 pag.176 https://www.ucamco.com/files/downloads/file/81/the_gerber_file_format_specification.pdf Valerio |
From: Linda H. <lh...@sh...> - 2018-06-01 11:15:20
|
> Could you please provide an example file name list? Section 11.4.1 of KiCAD's PCBNew manual, (version 4.0.7, August, 2017) provides the following example: xxxx-F_Cu.gbr for the component side. xxxx-B_Cu.gbr for the copper side. xxxx-F_SilkS.gbr for the component-side silkscreen markings. xxxx-B_SilkS.gbr for the copper-side silkscreen markings. xxxx-F_Paste.gbr for the component-side solder paste. xxxx-B_Paste.gbr for the copper-side solder paste. xxxx-F_Mask.gbr for the component-side solder mask. xxxx-B_Mask.gbr for the copper-side solder mask. The manual also mentions: "The format used by Pcbnew is RS274X format 4.6, Imperial, Leading zero omitted, Abs format. These are very usual settings." Here is an example of one of my rename scripts: mv Mark-B.Cu.gbr Mark-8.1.bc mv Mark-B.Mask.gbr Mark-8.1.bm mv Mark-B.SilkS.gbr Mark-8.1.bs mv Mark-F.Cu.gbr Mark-8.1.fc mv Mark-F.Mask.gbr Mark-8.1.fm mv Mark-F.SilkS.gbr Mark-8.1.fs mv Mark-Edge.Cuts.gbr Mark-8.1.ec mv Mark.drl Mark-8.1.df As I mentioned, I pretty much only work with 2 layer boards, so I have no idea what PCBNew generates for internal copper layers. > Are the suggested extensions listed here?: > https://www.protoexpress.com/content/gerber_extensions.jsp As I look through the manual, PCBNew's Gerber output options include "Use Protel filename extensions" which generates .gbl .gtl .gbs .gts .gbp .gtp .gbo .gto instead of .gbr for file name extensions. (I just tried this, and PCBNew also affixes the same file name suffices to its output with this option selected.) There is one other PCBNew option of note, "Include extended attributes". I just tried that too. I see the following relevant information in each of the files: gbl: %TF.FileFunction,Copper,L2,Bot,Signal*% gbs: %TF.FileFunction,Soldermask,Bot*% gbo: %TF.FileFunction,Legend,Bot*% gm1: %TF.FileFunction,Profile,NP*% gtl: %TF.FileFunction,Copper,L1,Top,Signal*% gts: %TF.FileFunction,Soldermask,Top*% gto: %TF.FileFunction,Legend,Top*% I just went looking... One of the board houses that I have used, SeeedStudio, recently changed their policy to accept the Protel file name extensions, however, they cannot accept files with any of the X2 file attributes, etc. since their CAM software can't read them. http://support.seeedstudio.com/knowledgebase/articles/1824574-how-to-generate-gerber-and-drill-files-from-kicad On 2018-06-01 01:19, Miklos Marton wrote: > >> >> KiCAD insists on writing out Gerbers with a file name suffix that >> indicates the layer. > Could you please provide an example file name list? >> However, my board house insists that all of the file names be the >> same, and that the file extension specify the layer. > Are the suggested extensions listed here?: > https://www.protoexpress.com/content/gerber_extensions.jsp > If not could you please share them? > > Thanks in advance! > |
From: Patrick F. <p.f...@ai...> - 2018-06-01 10:26:56
|
>From what I know detecting Gerber files based on their filename is a total pain. There are some libraries such as https://github.com/tracespace/whats-that-gerber/blob/master/index.js around which work in some cases. But in most cases it is just disappointing to the user. As mentioned before is this his issue already addressed by the Gerber X2 extensions. We recommend our users to use these which works out pretty well. In my opinion we should >only< support X2 extensions as it is the only solution which gives a fulfilling user experience. And it is a good way to increase popularity of Gerber X2. Just my two cents. On Fri, 1 Jun 2018 at 07:20 Miklos Marton <mar...@gm...> wrote: > > > > > KiCAD insists on writing out Gerbers with a file name suffix that > > indicates the layer. > Could you please provide an example file name list? > > However, my board house insists that all of the file names be the > > same, and that the file extension specify the layer. > Are the suggested extensions listed here?: > https://www.protoexpress.com/content/gerber_extensions.jsp > If not could you please share them? > > Thanks in advance! > > -- > Best regards, > Miklos Marton > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Gerbv-devel mailing list > Ger...@li... > https://lists.sourceforge.net/lists/listinfo/gerbv-devel > |
From: Miklos M. <mar...@gm...> - 2018-06-01 07:47:53
|
>> I will take a look. For the future it is better to separate patches on >> specific subjects. > I have added "Load all" functionality for drop files. > But I want to show all file names to be loaded on "Load all", and this > is not yet ready. > I have realized that the special characters of the dropped file urls got escaped. I have attached an updated patch to handle this. -- Best regards, Miklos Marton |
From: Miklos M. <mar...@gm...> - 2018-06-01 07:20:02
|
> > KiCAD insists on writing out Gerbers with a file name suffix that > indicates the layer. Could you please provide an example file name list? > However, my board house insists that all of the file names be the > same, and that the file extension specify the layer. Are the suggested extensions listed here?: https://www.protoexpress.com/content/gerber_extensions.jsp If not could you please share them? Thanks in advance! -- Best regards, Miklos Marton |
From: Linda H. <lh...@sh...> - 2018-05-31 21:16:27
|
> Any feedback, idea is welcome! I use KiCAD. I just looked into some Gerbers generated by KiCAD and there doesn't appear to be any kind of comment or attribute in any of the files that would betray the actual layer. (KiCAD is under heavy development, so things may have changed in recent versions.) KiCAD insists on writing out Gerbers with a file name suffix that indicates the layer. However, my board house insists that all of the file names be the same, and that the file extension specify the layer. So I have a script for that. I have two Gerbv project files named Front.gvp and Back.gvp (yeah, just 2 layer boards so far) with all of my layer ordering and coloring information for viewing in Gerbv. I copy these files from project to project and edit them to match the file names of my Gerber files. On 2018-05-31 11:03, Miklos Marton wrote: > Hello all, > > The following feature request got into my interest because I came across > the problem daily basis: > > https://www.sourceforge.net/p/gerbv/feature-requests/86/ > > To move forward I would like to create specifiation how to implement > this new feature. > > - We will need to introduce a layer index enumeration. For the cooper > layers there should be a single enum item in the middle of the enum list > (see next point). > > - For the cooper layers there should be an additional layernumber > ranging from 0 (outer top to outer bottom) > > - We will need to implement a function which would guess the layer index > (and layernumber for cooper layer) from the filename. To keep the user > experience at high level we need to collect the file naming conventions > for the most widespread CAM processors. I am familiar with the EAGLE so > I have opened a piratepad here and added the known output formats: > > http://piratepad.net/2Od3t5iofq > > Feel free to extend it with extensions/filename patterns from other > PCB tools. > > - It would be useful to group the opened layers per design (layers from > the same folder with different layerindex and same filename pattern > --where acceptible--). > > - When opening a new layer it will need to be decided if it belongs to a > group opened already: > In this case it should be inserted to the proper index of the found > group's layer order, otherwise it should be opened after the layers of > the current group. > > Any feedback, idea is welcome! > |
From: Sergey A. <aly...@gm...> - 2018-05-31 18:27:56
|
On Thu, May 31, 2018 at 8:48 PM, Valerio Messina via Gerbv-devel <ger...@li...> wrote: > On 31/05/2018 19:03, Miklos Marton wrote: >> >> - We will need to implement a function which would guess the layer index >> (and layernumber for cooper layer) from the filename > > .... >> >> Any feedback, idea is welcome! > > > guessing layer from file name can be difficult. > > Extracting it from 2014 Gerber X2 attributes is best: > https://en.wikipedia.org/wiki/Gerber_format Yes if it is X2 format (and there is patch for initial X2 support on sf.net). |
From: Sergey A. <aly...@gm...> - 2018-05-31 18:26:14
|
On Thu, May 31, 2018 at 8:03 PM, Miklos Marton <mar...@gm...> wrote: > - We will need to implement a function which would guess the layer index > (and layernumber for cooper layer) from the filename. To keep the user > experience at high level we need to collect the file naming conventions for > the most widespread CAM processors. I am familiar with the EAGLE so I have > opened a piratepad here and added the known output formats: Maybe use TinySCHEME regular expression or C regular expression library with separate configuration file, so file name rules won't be hardcoded. |