On Oct 7, 2014, at 10:48 AM, Nick Østergaard wrote:
>
> Den 07/10/2014 19.43 skrev "Wayne Stambaugh" :
> >
> > In Andy's defense, the OSX compile instructions show:
> >
> > # patch -p0 ../kicad/patches/wxwidgets-3.0.0_macosx.patch
> >
> > so I can understand his confusion. I missed that when I
Fixed this and the patch error in r5167
Wayne
On 10/7/2014 2:59 PM, Bernhard Stegmaier wrote:
> Yes, sorry… I also missed that.
> There is also another problem… copy/paste seems to have messed up
> closing quotes on the configure command:
> CPPFLAGS="-stdlib=libstdc++*"* \
> LDFLAGS="
Yes, sorry… I also missed that.
There is also another problem… copy/paste seems to have messed up closing
quotes on the configure command:
CPPFLAGS="-stdlib=libstdc++" \
LDFLAGS="-stdlib=libstdc++" \
Regards,
Bernhard
On 07.10.2014, at 19:48, Nick Østergaard wrote:
>
> Den 07/10/
On Oct 7, 2014, at 10:10 AM, Mike Crawford wrote:
> patch is expecting its input on stdin there, re-run the command with:
> patch -p0 < ../kicad/patches/wxwidgets-3.0.0_macosx.patch
> That should apply the patch
Hah, that worked.
Looks like a patch is needed for the patch instructions!
-a
On Oct 6, 2014, at 7:44 PM, Garth Corral wrote:
> On Oct 6, 2014, at 5:39 PM, Andy Peters wrote:
>
>> Hi, guys -- I have been doing daily builds on OS X, and I haven't had any
>> build issues. Now, I did build and install the various prerequisites (glew,
>> whatnot). Do recent builds use what
Den 07/10/2014 19.43 skrev "Wayne Stambaugh" :
>
> In Andy's defense, the OSX compile instructions show:
>
> # patch -p0 ../kicad/patches/wxwidgets-3.0.0_macosx.patch
>
> so I can understand his confusion. I missed that when I committed
> Bernhard's patch. I will update it so that it is correct.
In Andy's defense, the OSX compile instructions show:
# patch -p0 ../kicad/patches/wxwidgets-3.0.0_macosx.patch
so I can understand his confusion. I missed that when I committed
Bernhard's patch. I will update it so that it is correct. Sometimes
it's these setbacks that help us find issues and
Else, read the man page for patch, see the option -i.
Den 07/10/2014 19.26 skrev "Andy Peters" :
> On Oct 7, 2014, at 10:10 AM, Mike Crawford wrote:
>
> > patch is expecting its input on stdin there, re-run the command with:
> > patch -p0 < ../kicad/patches/wxwidgets-3.0.0_macosx.patch
> > Tha
patch is expecting its input on stdin there, re-run the command with:
patch -p0 < ../kicad/patches/wxwidgets-3.0.0_macosx.patch
That should apply the patch
On Tue Oct 07 2014 at 6:06:54 PM Andy Peters wrote:
> On Oct 6, 2014, at 7:44 PM, Garth Corral wrote:
>
> > On Oct 6, 2014, at 5:39 PM,
Hi Bernhard,
I sent the wrong link previously:
https://github.com/wayneandlayne/KicadOSXBuilder/tree/oct_2014_beta
Adam Wolf
Cofounder and Engineer, W&L
On Tue, Oct 7, 2014 at 7:07 AM, Adam Wolf
wrote:
> Bernhard,
>
> I have uploaded a build script at GitHub over at
> https://github.com/wayne
Bernhard,
I have uploaded a build script at GitHub over at
https://github.com/wayneandlayne/KicadOSXBuilder. It's nothing special,
but works for me.
Let me know what you think.
Adam Wolf
Cofounder and Engineer
W&L
On Tue, Oct 7, 2014 at 4:19 AM, Bernhard Stegmaier
wrote:
> Hi,
>
> and to an
Hi,
and to answer the first question: it now uses everything installed on
your system, the only dependency currently being built in the KiCad
CMake build process is boost.
But, as Garth already mentioned you must not use a "stock" wxWidgets,
because unfortunately still the overlay support is
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 t
On Oct 6, 2014, at 5:39 PM, Andy Peters wrote:
> Hi, guys -- I have been doing daily builds on OS X, and I haven't had any
> build issues. Now, I did build and install the various prerequisites (glew,
> whatnot). Do recent builds use what's installed on my system, or does the
> master CMake fi
Hi, guys -- I have been doing daily builds on OS X, and I haven't had any build
issues. Now, I did build and install the various prerequisites (glew, whatnot).
Do recent builds use what's installed on my system, or does the master CMake
file download and build the prerequisites as needed?
I jus
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
Hi Bernhard,
BZR5162 on OS X, pcbnew crashes on start.
Details of the crash are below.
Jean-Paul
AC9GH
Application: kicad
Version: (2014-10-02 BZR 5162)-product Release build
wxWidgets: Version 3.0.1 (debug,UTF-8,compiler with C++ ABI 1002,GCC 4.2.1,STL
containers,compatible with 2.8)
Platform:
It's committed! Many thanks to Bernhard for taking on the task of
fixing the OSX builds. Hopefully he can get the scripting working soon.
Once that is done, adding the documentation and libraries should be a
piece of cake :) He also graciously updated the OSX build instructions
so hopefully oth
Sent from my iPad
> On Oct 2, 2014, at 12:58 PM, Bernhard Stegmaier
> wrote:
>
> Yes, I didn’t do anything about documentation yet.
> It should be pretty easy to add if there is a way to copy/fetch/build it from
> CMake and put it to the bundle - just like the templates, etc.
>
> Same for t
On 10/2/2014 3:58 PM, Bernhard Stegmaier wrote:
> Yes, I didn’t do anything about documentation yet.
> It should be pretty easy to add if there is a way to copy/fetch/build it
> from CMake and put it to the bundle - just like the templates, etc.
>
> Same for the libraries/footprints.
> Speaking ab
Hi Bernhard.
Since BZR 5151, I cannot get any build of Kicad for OS X anymore.
As I deleted the executables, I am dead in the water.
I tried to build from your repository, and it does not build either.
What do you suggest as a build procedure from scratch?
I have deleted all the build directory
Yes, I didn’t do anything about documentation yet.
It should be pretty easy to add if there is a way to copy/fetch/build it from
CMake and put it to the bundle - just like the templates, etc.
Same for the libraries/footprints.
Speaking about releases, maybe there should be two in future (build op
The component and 3D model libraries are a good idea. If the user
doesn't like the github plugin, then you could also include the
footprint libraries. One thing I didn't see in Bernhard's patch was the
Documentation. That is definitely a must at some point in order to have
a stable release. I f
Sorry guys. I got sidetracked last night with some 3D stuff and I
didn't get it committed. I've 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,
Hi Adam,
it’s already on Wayne’s desk to commit…
Regards,
Bernhard
On 02.10.2014, at 20:37, Adam Wolf wrote:
> Hi Bernhard,
>
> Sorry to threadjack, but do you have any ETA on the patch that created that
> bundle? I'm extremely excited to release nightlies...
>
> Adam Wolf
> Cofounder and
Hi Garth,
see below.
Regards,
Bernhard
On 02.10.2014, at 18:23, Garth Corral 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 bundle. I know
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 bundle. I know it ultimately doesn’t matter to most
users as long as it runs and behaves properly but it doesn’t
2014-09-29 18:57 GMT+02:00 Bernhard Stegmaier :
> Hi,
>
> Currently the following paths should be used for “data” automatically
> (latest when my changes are submitted and what I found in the code):
>
> Base Paths (in order from top to bottom)
>
> $KICAD Environment variable
> ~/Library/Application
On 9/29/2014 12:59 PM, Jean-Paul Louis wrote:
> Wayne,
>
> Thank you for your prompt reply.
> I will remove the default plist key I created for KISYSPROJ.
>
> I will keep the KISYSMOD one until it is created during the OS X build.
> KIGITHUB should also be created when we select the libraries.
K
Wayne,
Thank you for your prompt reply.
I will remove the default plist key I created for KISYSPROJ.
I will keep the KISYSMOD one until it is created during the OS X build.
KIGITHUB should also be created when we select the libraries.
Just my $0.02,
Jean-Paul
AC9GH
On Sep 29, 2014, at 12:38 PM
Hi,
Currently the following paths should be used for “data” automatically (latest
when my changes are submitted and what I found in the code):
Base Paths (in order from top to bottom)
$KICAD Environment variable
~/Library/Application Support/kicad
/Library/Application Supprt/kicad
/Contents/Shar
On 9/29/2014 12:31 PM, Andy Peters wrote:
> On Sep 29, 2014, at 7:53 AM, Wayne Stambaugh wrote:
>
>> On 9/28/2014 10:20 PM, Adam Wolf wrote:
>>> I actually had this open in a tab for something else I was doing.
>>>
>>> https://developer.apple.com/library/mac/documentation/MacOSX/Conceptual/BPRunt
On 9/29/2014 11:49 AM, Jean-Paul Louis wrote:
> Wayne,
>
> This topic was already discussed in the kicad-users list when I was
> setting my Mac builds.
> I already posted Mac Environment files for KiCad using KISYSMOD,
> KISYSPROJ and KIGITHUB.
KISYSMOD only makes sense if footprint libraries are
On Sep 29, 2014, at 7:53 AM, Wayne Stambaugh wrote:
> On 9/28/2014 10:20 PM, Adam Wolf wrote:
>> I actually had this open in a tab for something else I was doing.
>>
>> https://developer.apple.com/library/mac/documentation/MacOSX/Conceptual/BPRuntimeConfig/Articles/EnvironmentVars.html
>>
>> At
On 9/28/2014 10:20 PM, Adam Wolf wrote:
> I actually had this open in a tab for something else I was doing.
>
> https://developer.apple.com/library/mac/documentation/MacOSX/Conceptual/BPRuntimeConfig/Articles/EnvironmentVars.html
>
> At the bottom of that page is an explanation how to set an envi
@lists.launchpad.net [kicad-developers@lists.launchpad.net]
Subject: Re: [Kicad-developers] OSX Build changes.
I actually had this open in a tab for something else I was doing.
https://developer.apple.com/library/mac/documentation/MacOSX/Conceptual/BPRuntimeConfig/Articles/EnvironmentVars.html
At the bottom of
I actually had this open in a tab for something else I was doing.
https://developer.apple.com/library/mac/documentation/MacOSX/Conceptual/BPRuntimeConfig/Articles/EnvironmentVars.html
At the bottom of that page is an explanation how to set an environment
variable for an app bundle.
I am so, so e
On 9/28/2014 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.
> F
>
> From: Bernhard Stegmaier
>To: KiCad Developers
>Sent: Monday, September 29, 2014 2:31 AM
>Subject: [Kicad-developers] OSX Build changes.
>
>
>
>Hi all,
>
>
>as Wayne already mentioned below I made some major changes
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 is
40 matches
Mail list logo
