of
the error at the end of the “make”.
I will create the files for the ENV variables, and let you know how that
works.
Regards,
Jean-Paul
On May 23, 2014, at 10:59 AM, Bernhard Stegmaier stegma...@sw-systems.de
[kicad-users] kicad-us...@yahoogroups.com wrote:
Hi Jean-Paul,
can you tell
Hi,
build on OSX is broken since rev. 4895 (I guess)…
The include glu.h is not found because __DARWIN__ is not set. Moving the
include of glcanvas.h from the .cpp to the beginning of the header seems to fix
this. Further, it seems as if no special library is needed to link against -
/2014 12:14, Bernhard Stegmaier a écrit :
Hi,
when building on OSX with KICAD_BUILD_DYNAMIC=ON the last step making the
app bundle portable fails for an out-of-tree build and doesn’t support
.kiface yet.
The attached patch
* Fixes/supports out-of-tree builds
* Adds support for also fixing
Hi,
clang seems to be much more picky than gcc… attached a patch that fixes 2
warnings I spotted during my last build experiments (being obviously really a
bug).
I don't know what it will improve, though.
Regards,
Bernhard
warnings.diff
Description: Binary data
Hi,
building with clang (at least on OSX) and -Wall is really noisy so that you can
hardly see what’s going wrong.
So, I decided to fix the warnings… attached are 3 patches I prepared (against
rev. 4911):
*** clang-warnings-1.diff:
Everything that probably should be fixed:
* Disable
of warnings I have switched off via compile switch both build for
me.
On OSX, I have:
Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)
Regards,
Bernhard
On 03.06.2014, at 00:32, Tomasz Wlostowski tomasz.wlostow...@cern.ch wrote:
On 02.06.2014 19:52, Bernhard Stegmaier wrote:
Hi
Hi,
Jean-Paul found a crash of bitmap2component on exit while testing some of my
changes.
Problem was not related to my changes but obviously introduced with main branch
rev. 4941.
A fix/workaround is here:
http://bazaar.launchpad.net/~stegmaier/kicad/kicad-osx/revision/4945
Regards,
Hi,
while fixing some clang compile warnings I added an obviously missing const to
GetScreen() in pl_editor_frame.h (part of
http://bazaar.launchpad.net/~stegmaier/kicad/kicad-osx/revision/4936) to fix an
overloaded virtual warning.
This forced the compiler to now really take the function
Hi,
the same behavior is IMHO there in many (at least some) other places using
combo boxes not only with pcbnew.
I have used only eeschema lately… but there I found it very annoying in the
library editor pin properties dialog (that’s one place I remember for 100%).
Everything in there with a
Hi,
just FYI… I am using 3.0.1 on OSX since it has been published.
I used eeschema quite a lot since then, pcbnew not so much.
I never did see any problem with it…
Regards,
Bernhard
On 06.09.2014, at 16:49, Wayne Stambaugh stambau...@verizon.net wrote:
On 9/5/2014 5:04 PM, Andrew Zonenberg
Hi,
how did you install wxWidgets, which version are you using?
I just synced and tested… works for me without problems, I use
-DwxWidgets_CONFIG_EXECUTABLE=../wxWidgets/3.0/bin/wx-config
to point CMake to my wxWidgets build.
Regards,
Bernhard
On 27.09.2014, at 07:12, Jean-Paul Louis
:
Thank you Bernhard.
I will try to modify my script with this switch and test it.
Jean-Paul
AC9GH
On Sep 27, 2014, at 11:48 AM, Bernhard Stegmaier stegma...@sw-systems.de
wrote:
Hi Jean-Paul,
look into Wayne’s mail… to use the “old” all-in-one build by Marco you
explicitly have
KICAD_SCRIPTING_MODULES=OFF
KICAD_SCRIPTING_WXPYTHON=OFF
USE_FP_LIB_TABLE=HARD_CODED_ON
BUILD_GITHUB_PLUGIN=ON
On Sep 27, 2014, at 5:14 PM, Bernhard Stegmaier stegma...@sw-systems.de
wrote:
Hi,
I know that… that happens if you don’t apply
,
Jean-Paul
AC9GH
On Sep 28, 2014, at 7:02 AM, Bernhard Stegmaier stegma...@sw-systems.de
wrote:
Hi,
yes, you shouldn’t… the old build process should do (or, at least, did) that.
I am done with restructuring bundles for the new way of building.
I have to check/fix the old way
Hi all,
as Wayne already mentioned below I made some major changes to the creation of
OSX application bundles in the build process.
The most obvious is that now only one application bundle is created which
starts the kicad launcher.
From there you can go anywhere else.
The created bundle now
12:31 PM, Bernhard Stegmaier wrote:
Hi all,
as Wayne already mentioned below I made some major changes to the
creation of OSX application bundles in the build process.
The most obvious is that now only one application bundle is created
which starts the kicad launcher.
From there you can go
Hi,
either set $PATH in the shell where you build in a way that wx-config can be
found (i.e., to your wxWidgets/bin folder) or use
-DwxWidgets_CONFIG_EXECUTABLE=path/to/your/wx-config
switch with kicad (this works for me on OSX, but should also be the same for
Linux).
Regards,
Bernhard
On
Why don’t you try
-DwxWidgets_CONFIG_EXECUTABLE=path/to/your/wx-config
as I suggested?
This works for me all the time.
Regards,
Bernhard
On 01.10.2014, at 04:16, inkblotter inkbot...@gmail.com wrote:
Wayne,
I tried at r5159 and got exactly the same errors as I wrote about below.
Hi,
/opt/local/Library looks like a MacPorts installation.
You won’t be happy with that because it is missing the needed wxOverlay patches.
Further, MacPorts seems to do the Framework stuff wrong (besides wxWidgets
itself messing up the library names in OSX builds). CMake BundleUtilities as
Maybe you should try an out-of-tree build (create a separate build directory
and call cmake from there) and completely wipe out the build directory whenever
you change path or compile switches.
Sometimes some things get left behind causing problems.
Regards,
Bernhard
On 01.10.2014, at 23:11,
Hi Garth,
see below.
Regards,
Bernhard
On 02.10.2014, at 18:23, Garth Corral gcor...@abode.com wrote:
Hi Bernhard,
I looked around through the application bundle you posted and had some
questions about the proposed layout. It seems there is some arbitrary
placement of files in the
Cofounder and Engineer
Wayne and Layne LLC
On Oct 2, 2014 1:29 PM, Bernhard Stegmaier stegma...@sw-systems.de wrote:
Hi Garth,
see below.
Regards,
Bernhard
On 02.10.2014, at 18:23, Garth Corral gcor...@abode.com wrote:
Hi Bernhard,
I looked around through the application
already tested to make sure it didn't
break windows or linux builds so it's ready to commit. I will do my
best to get it committed this evening when I get home from work.
Wayne
On 10/2/2014 2:38 PM, Bernhard Stegmaier wrote:
Hi Adam,
it’s already on Wayne’s desk to commit
Hi,
most of your observations are as far as I can see not a problem of the bundles
itself, but of the KiCad modular concept (kiface).
When you launch pcbnew et al. from KiCad launcher the correct “application” is
only loaded as a module, so the main application is still kicad launcher and I
, Bernhard Stegmaier stegma...@sw-systems.de wrote:
Hi,
most of your observations are as far as I can see not a problem of the
bundles itself, but of the KiCad modular concept (kiface).
When you launch pcbnew et al. from KiCad launcher the correct “application”
is only loaded as a module
On 04.10.2014, at 15:17, Wayne Stambaugh stambau...@verizon.net wrote:
On 10/4/2014 4:26 AM, Bernhard Stegmaier wrote:
Hi,
most of your observations are as far as I can see not a problem of the
bundles itself, but of the KiCad modular concept (kiface).
When you launch pcbnew et al. from
a
terminal is started in which then pcbnew is executed.
Regards,
Bernhard
On 04.10.2014, at 15:56, Bernhard Stegmaier stegma...@sw-systems.de wrote:
There are 2 possibilities as far as I can see:
(1) One single application bundle - like it is now.
There are probably still some cosmetic issues
Stambaugh stambau...@verizon.net wrote:
On 10/4/2014 4:26 AM, Bernhard Stegmaier wrote:
Hi,
most of your observations are as far as I can see not a problem of the
bundles itself, but of the KiCad modular concept (kiface).
When you launch pcbnew et al. from KiCad launcher the correct
, at 6:56 AM, Bernhard Stegmaier stegma...@sw-systems.de
wrote:
There are 2 possibilities as far as I can see:
(1) One single application bundle - like it is now.
There are probably still some cosmetic issues as Garth told, but I think
these are just minor inconsistencies that could be sorted
Hi Jean-Paul,
I didn’t see something like this up to now.
There is one strange thing… you seem to use Boost 1.56, whereas KiCad only
ships with 1.54.
That’s the only dependency that currently is still being built by KiCad (as far
as I know Wayne is working on removing that, but I have not seen
At least I can confirm this behavior with my CMake 2.8.12.
If I run the same configure command twice in a row, the second one will fail
just as for Adam.
If I only run it once, do a make, then change something in CMake files and
again issue a make then CMake automatically re-runs and everything
Hi,
yes, this patch/fix is included in the 3 wxWidget-patches mentioned in
mac-osx.txt.
Note, that it is not 1:1 the same fix, but AFAIK addresses the same problem (if
building wxWidgets with those 3 patches doesn’t solve your problem, please
tell).
Thanks for the note on the icons… I’ll put
is missing. So, you have
to patch/build your own version as described in mac-osx.txt.
If you can wait a bit, there will be a small script doing this for you
coming with my next changes...
Regards,
Bernhard
On 2014-10-07 07:17, Bernhard Stegmaier wrote:
Hi,
yes, this patch/fix is included
Hi all,
I had a look at the icon issue on OSX that Andy mentioned below.
Behavior is to be expected as described, because for the single KiCad
application bundle only the .pro extension/icon is registered.
So, I added pcbnew extensions/icons to test.
If I now drag/drop a .kicad_pcb file to the
with
pcbnew. If this is the desired behavior that OSX users require, than
you may have to modify you bundle layout to accommodate this. I'll
leave that up to the OSX users to decide what makes the most sense.
On 10/10/2014 1:55 PM, Bernhard Stegmaier wrote:
Hi all,
I had a look at the icon issue
with the wrong drawing.
When each app had it’s own bundle, it was working almost OK.
I still do not understand why the right click in the kicad manager shows an
edit option, but that option never worked on all my builds.
Just my $0.02,
Jean-Paul
AC9GH
On Oct 10, 2014, at 3:00 PM, Bernhard
Hi,
normally, this error happens if you mix up different versions of C++ standards
(the “-std=...” option) or you mix linking against libcpp/libstdc++ in
KiCad/Dependencies.
You will have to find out what homebrew uses for the various dependencies and
configure it in a way that everything is
:56, Bernhard Stegmaier stegma...@sw-systems.de wrote:
Hi,
normally, this error happens if you mix up different versions of C++
standards (the “-std=...” option) or you mix linking against libcpp/libstdc++
in KiCad/Dependencies.
You will have to find out what homebrew uses for the various
Hi,
if I understood the script right, then it replaces the whole stock cmake build
configuration of KiCad with its own version… so this is way more than the usual
one-script-to-build-everything scripts.
Everybody using it should be really aware of this… I guess there won’t be any
official
/view/head:/Documentation/compiling/mac-osx.txt
On 10/11/2014 11:06 AM, Bernhard Stegmaier wrote:
… and another comment:
As far as I can see this recipe uses/depends on a pretty stock “Wxmac”
recipe.
I doubt that all the needed patches for KiCad are included in this Wxmac
recipe
\
Bobs-MacBook-Air:scripts bobgus$
wxWidget just finished compiling - will stick it into kicad now.
Thanks much
Bob G
On 10/11/2014 01:17 PM, Bernhard Stegmaier wrote:
Yes.
IMPORTANT:
At the moment you *must not* use a wxWidgets/wxPython version installed by
any
package manager
I can’t confirm that with the rev. 5173 I am currently working on (which some
improvements fixes, but none of that should fix such a behavior). None of the
changes 5173-5176 looks like they would cause something like that.
I’ll push my changes to Wayne next days, you might want to try then.
I
?
2014-10-12 23:44 GMT+02:00 Garth Corral gcor...@abode.com:
This is not new; I saw it as far back as 5151. I didn’t correlate it with
any sort of launch order, though, and I wasn’t able to reproduce it.
Garth
On Oct 12, 2014, at 1:17 PM, Bernhard Stegmaier stegma...@sw-systems.de
wrote:
I
No. That change was done on intention - everything is in a single
bundle/application now to avoid duplicating all the libraries or
inter-application dependencies introduced by symlinks (as it was before).
At the moment you just can start everything via the KiCad launcher.
My next changes will
As I said before, I never had this problem with my builds, even Jean-Paul
didn’t have this problem with one of my builds.
Yesterday, I completely updated my build machine:
OSX 10.9.5, Xcode 6.0.1, all new MacPorts for the dependencies (I also changed
build flags to -x11 and +quartz, before I
KiCad carries every library it depends on in the bundle (in contrast to
e.g., linux).
So, as long as the system libraries (not contained in the bundle) don't
break anything badly/incompatible, a version compiled on Mavericks or
any other OSX should work just fine. I guess breaking something
Hi,
I didn’t use any other version of boost… always use the custom version that
still comes with KiCad.
I also did a lot of builds recently, mostly with -j4 and never had problems
with that…
Regards,
Bernhard
On 21.10.2014, at 21:41, Wayne Stambaugh stambau...@verizon.net wrote:
Adam,
to
believe that we have been bit by the missing files generated by
make_lexer() before now because none of the generated files are marked
as dependencies when building their respective targets. I should have a
fix later today but I have some testing to do.
On 10/22/2014 1:59 AM, Bernhard
Hi,
yes, that fixes it.
Regards,
Bernhard
On 24.10.2014, at 22:59, Wayne Stambaugh stambau...@verizon.net wrote:
Bernhard,
Can you please verify that this patch does indeed fix the issue on OSX
before I add this patch.
Thanks,
Wayne
On 10/23/2014 11:12 PM, Garth Corral wrote:
On 25.10.2014, at 23:45, Wayne Stambaugh stambau...@verizon.net wrote:
On 10/25/2014 5:14 PM, Brian Sidebotham wrote:
On 25 October 2014 17:22, Wayne Stambaugh stambau...@verizon.net wrote:
I think both modules directories should be changed now to footprint.
We've made the decision to
Hi,
I think it is useful to collect all the various patches in the “patches”
folder… so you don’t have to find them on the net yourself.
I am not quite sure if they should be included in the small wxWidgets build
script.
Only goal of the script is to save some typing… if you put all the
Hi,
yes, it should work with all “standalone” apps (at least, it does for me).
The top-level apps are just links to the real app bundles sitting inside the
main bundle (kicad.app/Contents/Applications/pcbnew.app).
It is implemented in a way that it loads the kiface-dsos always relative to the
Hi Adam,
great!
I collected what paths are now used for various things around the code.
I’ll write this down this weekend, you could then add this to the readme.
I guess this would be great help for someone setting it up the first time… it’s
not that easy when you don’t know where to put what.
that didn't kill the job.
Adam Wolf
Cofounder and Engineer
WL
On Thu, Oct 30, 2014, 12:59 PM Andy Peters de...@latke.net wrote:
On Oct 30, 2014, at 8:15 AM, Bernhard Stegmaier stegma...@sw-systems.de
wrote:
You *must* do a “make install” and use that binaries/links (also, all
Peters de...@latke.net wrote:
On Oct 30, 2014, at 8:15 AM, Bernhard Stegmaier stegma...@sw-systems.de
wrote:
You *must* do a “make install” and use that binaries/links (also, all the
bundling/relocatong of libs is only done on the binaries created during
install)…
Slight swerve here
working on layout, so each time I want to look at the schematic, I have to
exit KiCad, and then load the schematic, and after load pcbnew.
This is really frustrating, and I hope you OS X gurus, will fix it as it was
OK before.
Jean-Paul
AC9GH
On Oct 30, 2014, at 11:20 AM, Bernhard Stegmaier
from Kicad.app but not from PCBNew.app.
Does this tell us anything about what went wrong?
Adam Wolf
On Thu, Oct 30, 2014 at 1:57 PM, Bernhard Stegmaier stegma...@sw-systems.de
wrote:
Yes.
All the dependency relocation stuff is done in the install step.
You can run kicad launcher
.
Adam Wolf
Cofounder and Engineer
WL
On Thu, Oct 30, 2014 at 2:23 PM, Bernhard Stegmaier stegma...@sw-systems.de
wrote:
Can you put the build somewhere?
I would like to try it… maybe I can see something being wrong?
Regards,
Bernhard
On 30.10.2014, at 20:16, Adam Wolf adamw
… I just did a quick non-scripting build of a clean head revision (5240).
No problems, pcbnew starts from launcher and standalone… links and bundle
structure also are created as it is intended to be.
Regards,
Bernhard
On 30.10.2014, at 20:51, Bernhard Stegmaier stegma...@sw-systems.de wrote
Hi all,
I am reworking the WX_OVERLAY stuff for OS X in eeschema to (hopefully) get rid
off the annoying redraw artifacts.
Looks quite good now, but I stumbled over some different/inconsistent behaviors
and I don’t know if these are due to my changes or it is everywhere the same.
Maybe some
(2a) eeschema: Block Move:
When doing a block move everything of the block is drawn in black, similar
to “grab from (1) but different to normal “move”.
And this, the wires and the symbol is black here.
(2b) eeschema: Block Move:
When doing a block move original content is still shown
On 30.10.2014, at 22:40, Nick Østergaard oe.n...@gmail.com wrote:
Hmm, ok, but what I see on my side was tested with 5217 and wx 3.0.2.
Should my build be newer?
No, thanks… No relevant changes in that area I guess. I have seen those things
already some months back when I tried my changes
Hi,
works perfect for me… with trackpad and also Magic/Mighty Mouse (without
pinch-to-zoom for the mice of course).
Tested with the pinch-to-zoom wxWidgets patch on 3.0.2, KiCad changes merged
into 5249.
I would really love to see this getting merged to main line.
It not only makes panning
Hi all,
I am still trying to find out/optimize where what is being loaded from
(especially for OS X).
In common/kiface_i.cpp the global search stack for pcbnew is initialized with
…/modules
…/modules/packages3d
with “…” being some OS specific base paths.
The global search stack seems to be
of templates, scripts, xml-Files for BOM,
etc.) and where they should be located?
Regards,
Bernhard
On 03.11.2014, at 00:33, Wayne Stambaugh stambau...@verizon.net wrote:
On 11/2/2014 4:25 PM, Bernhard Stegmaier wrote:
Hi all,
I am still trying to find out/optimize where what is being loaded
On 03.11.2014, at 14:53, Wayne Stambaugh stambau...@verizon.net wrote:
On 11/3/2014 3:22 AM, Cirilo Bernardo wrote:
On Mon, Nov 3, 2014 at 6:19 PM, Bernhard Stegmaier
In general, is there anywhere a list of “supplemental” files
(libraries, 3d-models, footprints, various kinds
Hi Adam,
can you send me the output of the “make install” command?
This uses CMake functions similar to what macdylibbundler does… and for me it
relocates all non-standard libs to the bundle.
Regards,
Bernhard
On 05.11.2014, at 20:55, Adam Wolf adamw...@feelslikeburning.com wrote:
Hi folks,
.
Adam Wolf
Cofounder and Engineer
WL
On Wed, Nov 5, 2014 at 2:46 PM, Adam Wolf adamw...@feelslikeburning.com
wrote:
Hi Bernhard,
Thank you! Here is the make install output: http://pastebin.com/pPSNTLv5
Adam Wolf
Cofounder and Engineer
WL
On Wed, Nov 5, 2014 at 2:35 PM, Bernhard
Great job, Adam.
My vote is for the separate dmg image for libraries.
As a normal OSX user you won’t do anything inside the bundle, so I think it is
more easy to just grab the library.dmg and pull contents to the
~/Library/Application Support/kicad/library folder.
Changing things inside the
Yes, one .dmg is also fine with me.
We shouldn’t put anything into the bundle that a user can change (like adding
his own symbol to a predefined library, etc.).
If the changes are stored in files inside the bundle itself then they will just
get lost when a user tries to update the usual way
I can check on OSX…
On 06.11.2014, at 20:19, Wayne Stambaugh stambau...@verizon.net wrote:
On 11/6/2014 2:01 PM, Garth Corral wrote:
Yes, sorry, OS X. I’ll add the version information to the bug and include
it in the future.
That's why I didn't see it. If someone with OSX could verify
...
Adam Wolf
Cofounder and Engineer
On Thu, Nov 6, 2014 at 12:59 PM, Andy Peters de...@latke.net wrote:
On Nov 6, 2014, at 11:51 AM, Bernhard Stegmaier stegma...@sw-systems.de
wrote:
Yes, one .dmg is also fine with me.
We shouldn’t put anything into the bundle that a user can change
… applies, builds, and fixes the problem (tested with rev. 5249).
Regards,
Bernhard
On 06.11.2014, at 20:25, Bernhard Stegmaier stegma...@sw-systems.de wrote:
I can check on OSX…
On 06.11.2014, at 20:19, Wayne Stambaugh stambau...@verizon.net wrote:
On 11/6/2014 2:01 PM, Garth Corral
,
Bernhard
On 08.11.2014, at 20:57, Nick Østergaard oe.n...@gmail.com wrote:
Hi Bernhard
What is your status on this drawing issue?
I am thinking linking this to the bug in
https://bugs.launchpad.net/kicad/+bug/1381864
Nick
2014-10-30 22:44 GMT+01:00 Bernhard Stegmaier stegma...@sw
I tried to build against a stock trunk boost some while back (at least a couple
of months), but that failed in KiCad itself because of some interface changes
in boost… I don’t know if that was beyond 1.57 or things in KiCad have already
been adapted.
If we would like to drop 1.54, somebody
Hi,
I can't tell at the moment, I will try how if/it works.
I did use external boost some while back, but I can't exactly remember
how I did it...
Regards,
Bernhard
On Wed, 2014-11-12 at 12:44 -0500, Wayne Stambaugh wrote:
On 11/12/2014 11:33 AM, Bob Gustafson wrote:
I tried doing this on
, Bernhard Stegmaier stegma...@sw-systems.de wrote:
Hi,
I can't tell at the moment, I will try how if/it works.
I did use external boost some while back, but I can't exactly remember how I
did it...
Regards,
Bernhard
On Wed, 2014-11-12 at 12:44 -0500, Wayne Stambaugh wrote:
On 11/12
set to 10.6 in your build script as far as I remember...
Regards,
Bernhard
On 12.11.2014, at 20:20, Bernhard Stegmaier stegma...@sw-systems.de wrote:
OK, so I installed boost from MacPorts as I do with the other dependencies.
Just a simple “sudo port install boost” which did install boost 1.56
Hi all,
eeschema still has some not so bad but nevertheless annoying redraw bugs on OS
X (using WX_OVERLAY), e.g., doing a rotate during a move.
In the branch
lp:~stegmaier/kicad/kicad-eeredraw
https://code.launchpad.net/~stegmaier/kicad/kicad-eeredraw
I reworked current WX_OVERLAY handling
Hi OSX guys,
do you still see the red blob bug” in latest revisions (since yesterday)?
I still had it in all the builds I made, the last revision I built was 5263,
and it was in there.
When I switched to external boost for the avhttp tests (this build has the red
blob problem) I noticed that
patch that set macosx-version-min to
10.7 for everything. When I read this I tried building again without that
patch and sure enough, red blob. When I rebuilt with version-min set to 10.7
it went away again.
Garth
On Nov 16, 2014, at 12:41 AM, Bernhard Stegmaier stegma...@sw-systems.de
Hi Wayne,
yes, it was behind that changes.
Updated to 5288.
Thanks,
Bernhard
On 16.11.2014, at 02:10, Wayne Stambaugh stambau...@verizon.net wrote:
On 11/15/2014 11:13 AM, Bernhard Stegmaier wrote:
Hi all,
eeschema still has some not so bad but nevertheless annoying redraw bugs on
OS
if any of the devs have a 10.6 machine to test on--I
certainly don't!
Thoughts?
(This may be the last blocker bug of any difficulty. Docs and libraries
included are the last two I know of, but they will be straightforward. Great
work!)
On Nov 16, 2014 5:10 AM, Bernhard Stegmaier
included are the last two I know of, but they will be straightforward.
Great work!)
On Nov 16, 2014 5:10 AM, Bernhard Stegmaier stegma...@sw-systems.de
mailto:stegma...@sw-systems.de wrote:
Yes, sounds reasonable… I was wrong about 10.8, libc++ seems to be there
since 10.7.
I
(on non-OSX
platforms), because the artifacts of that report look quite similar to what my
changes seem to have brought up for you...
Regards,
Bernhard
On 16.11.2014, at 17:27, Wayne Stambaugh stambau...@verizon.net wrote:
On 11/16/2014 10:10 AM, Bernhard Stegmaier wrote:
Hi Wayne
.
With your branch, there the artifacts gets copied to each position the
symbols is moved to. I can make quite a mess (snake?).
Nick
2014-11-16 22:17 GMT+01:00 Bernhard Stegmaier stegma...@sw-systems.de:
Hmm.
Does Windows use the USE_WX_GRAPHICS_CONTEXT or is it just the same as
Linux?
I
artifacts
(overlapping segments that now look “solid” because of being drawn with COPY
might not look like that when always drawn using XOR).
Regards,
Bernhard
On 17.11.2014, at 00:24, Nick Østergaard oe.n...@gmail.com wrote:
2014-11-16 23:47 GMT+01:00 Bernhard Stegmaier stegma...@sw-systems.de
Hi,
since help files is something directly used/delivered with KiCad (nothing that
a user can/will change), shouldn’t this directly go into the bundle.
E.g., kicad.app/Contents/SharedSupport/help?
If you put on the same level as kicad.app, you can’t move kicad.app around as
you like I guess
,
Bernhard
On 18.11.2014, at 07:35, Bernhard Stegmaier stegma...@sw-systems.de wrote:
Hi,
since help files is something directly used/delivered with KiCad (nothing
that a user can/will change), shouldn’t this directly go into the bundle.
E.g., kicad.app/Contents/SharedSupport/help?
If you put
Oh boy, much to read… :)
Be prepared, this will be a long reply.
First, come on, Adam. You did an awesome job setting up the Jenkins and being
willing to provide automated builds. Please don’t throw that away. It’s just a
technical discussion…
=== Is OSX so different than Linux? ===
No, it
Wolf
On Tue, Nov 18, 2014, 12:45 PM Bernhard Stegmaier stegma...@sw-systems.de
wrote:
Oh boy, much to read… :)
Be prepared, this will be a long reply.
First, come on, Adam. You did an awesome job setting up the Jenkins and being
willing to provide automated builds. Please don’t throw
Great!
My last scripting build was ~200MB uncompressed size, so percentage would get
better.
But hey, it’s like SW development in theory… only 30% is coding, the rest is
paperwork… :)
I will meanwhile keep my eyes open how other applications handle this.
Xcode provides an extra download menu
On 19.11.2014, at 17:28, Wayne Stambaugh stambau...@verizon.net wrote:
On 11/18/2014 3:34 PM, Bernhard Stegmaier wrote:
Hi,
I don’t know yet… maybe it is only OS X related, maybe not…
Some weeks ago Jean-Paul reported a weird “pcbnew crashes always on
start” problem:
https
On 19.11.2014, at 18:59, Wayne Stambaugh stambau...@verizon.net wrote:
On 11/19/2014 12:38 PM, Bernhard Stegmaier wrote:
cd build_folder
make clean# clean any source files generated by CMake
I didn’t do the make clean, ...
rm -rf *
… but after that the folder
Hi all,
the attached bzr-bundle/patch (against 5302) removes the hard-coded
“-mmacosx-min-version=10.5” parameters for KiCad, internal boost, and wxWidgets
build script.
Instead, it is now required to specify the target version using the existing
CMake parameter
Hi all,
before the overhaul of the 3D-Viewer some while back it showed on silkscreen
only what I did draw on it.
In particular, it didn’t show values/references (maybe just because I switched
off rendering of values/references in pcbnew?).
Now, it seems to always show values/references… if I
Hi,
I will try to find out if no one has an idea about it…
I just asked if someone has an idea so that maybe I wouldn’t have to start from
scratch (or, just fix some forgotten spots).
At least in eeschema it got fixed somehow, but maybe not on purpose but just as
a side effect…
Regards,
Hi Jean-Paul,
I built bzr5307 yesterday with external boost 1.56 without any problems.
I didn’t try internal 1.54 because that would cause problems having another one
installed (as posted some while ago).
But, IMHO it didn’t fail in boost but just in some of the icons using clang++
for the
This
/Volumes/Drobo/Projects/kicad-build/wx-bin/include/wx-3.0/wx/strvararg.h:30:18:
fatal error: 'tr1/type_traits' file not found
#include tr1/type_traits
^
1 error generated.
is almost for sure a sign that you compiled wxWidgets with a different C++
standard
I am using boost 1.56 from MacPorts.
I checked it and as far as I can see there are no relevant patches used like
with the KiCad internal boost.
Regards,
Bernhard
On 02.12.2014, at 06:11, LordBlick lordbl...@gmail.com wrote:
In response to a message written on 01.12.2014 19:14, from Bernhard
1 - 100 of 506 matches
Mail list logo
