| ID: | 3471 |
| From: | ge...@igor2.repo.hu |
| Date: | Sat, 19 Oct 2019 04:29:34 +0200 (CEST) |
| Subject: | Re: [pcb-rnd] Windows XY export was experimental windows port - |
| in-reply-to: | 3470 from Bob Paddock <gr...@gmail.com> |
On Fri, 18 Oct 2019, Bob Paddock wrote: >> Most probably you want to modify the icon so that it sets CWD to your home >> dir. I am not sure how windows is then doing the DLL search, whether it >> would find the DLLs next to the exe, so please try it and report if it >> worked or not. > >If it is not using the DLLs next to exe then it would be considered a >security violation as a DLL injection attack. >This is why nothing should ever be written to the /bin directory after install. >DLL's in arbitrary paths should not be executed. I mean: 1. cd /home/foo 2. execute /usr/bin/pcb-rnd.exe question is whether windows will be able to find bar.dll, required by pcb-rnd.exe, placed in /usr/bin while your CWD is not /usr/bin but /home/foo. All this while your /usr/bin is _not_ on the $PATH (or %PATH% if windows still doing the DOS style env vars). If that works, you should do this setup in your icon. Is such an icon stored in a plain file? If so, and you manage to craft a working icon, please share! >> It implements a syntax that lets you tell the exporter what layers to >> export in what file. For more info: >> http://repo.hu/cgi-bin/pool.cgi?cmd=show&node=cam > >That explained why CAM exists. >Some actual examples would be helpful in it. The first link in the body of above index/summary/dispatch document brings you to: http://repo.hu/projects/pcb-rnd/user/06_feature/cam/ This has the detailed specification of what CAM can do for you, the exact syntax and examples. The above page is part of our user manual. pcb-rnd does have an user manual, and while it is not complete, it does document a large part of pcb-rnd: http://repo.hu/projects/pcb-rnd/user I think it is worth reading the user manual especially before you start using advanced feautres like CAM. For example CAM is a whole domain specific language. The efficient way of learning such a language is reading the spec and looking at examples while doing so. I believe such things can't be just picked up from tooltips or learned from the GUI dialogs. (I also recommend every user to read especially chapter 2, the data model part - without that, it's pretty much impossible to understand what subcircuits and padstacks are and how they interact with other objects and how the layer representation is. Having geda background doesn't bypass this because these things changed a lot since the geda days.) >> You can use it to do fancy things, like (random example) export only top >> silk and top copper layer groups combined to an svg file. > >>From reading the various links from there I'd expect the GUI cam filed >to be a job script to run, >not the name of a file that contradicts what the top of the dialog >shows for the path. >At the vary least overwrite the path the dialog shows when the cam >filed is filled in. >Just seems like a confusing way to rename a file at the moment to me, >as on Windows that is all I'm seeing it do. I think you are mixing cam jobs with the cam field of direct exporting. The two are specified in different sections of the doc and the terminology in the doc is clear. Where you entered DSN is the cam field (the cam option) of an export plugin - no cam jobs involved. The CAM field does a lot more than setting the file name. When cam is specified, it does override the file name _and_ some other fields too, and that's intentional. That is override, not contradiction. The gui will not try to figure this, and that is intentional too. CAM is an optional, advanced feature. Please either read the doc so you fully understand how it works, or if you don't need CAM exports, just ignore the whole CAM subsystem and use the old way. (When you need CAM is described in the original link I sent.) >For files that have no layers like BOM and XY I still find the >behavior I'm seeing odd. That part is well sepcified too, and even the reason why we need this is documented in the same user manual at http://repo.hu/projects/pcb-rnd/user/06_feature/cam/ Regards, Igor2
Reply subtree:
3471 Re: [pcb-rnd] Windows XY export was experimental windows port - from ge...@igor2.repo.hu