On 10/11/2014 01:00 AM, Mark Roszko wrote:
The build compiles fine for me, did you run cmake configure properly?
Cmake generates shader_src.h which shader.cpp includes and has all the
missing variables you see the errors complaining about.
Yes, and for me too. The error I got was caused by som
The build compiles fine for me, did you run cmake configure properly?
Cmake generates shader_src.h which shader.cpp includes and has all the
missing variables you see the errors complaining about.
___
Mailing list: https://launchpad.net/~kicad-developers
After bzr up and make clean && make -j10
..
[ 38%] Built target shader_headers
[ 38%] Building CXX object common/CMakeFiles/gal.dir/gal/opengl/shader.cpp.o
/home/jfm/build/kicad/kicad.bzr/common/gal/opengl/shader.cpp: In member
function ‘bool KIGFX::SHADER::LoadBuiltinShader(unsigned in
Hi,
This patch makes the changes to add a selection button to the simple
dialog that appears when you right-click on a component and choose
Edit Component > Footprint. The button will open the footprint
browser. This is just like the component property editor having the
assign footprint button.
+
> On Oct 10, 2014, at 3:13 PM, Bernhard Stegmaier
> wrote:
>
> I noticed the caching problem about 1 year ago when I played around with the
> retina setting in the Info.plist for KiCad.
> I had built KiCad and launched it => non retina settings (OK, was not
> correctly configured).
> I chang
I noticed the caching problem about 1 year ago when I played around with the
retina setting in the Info.plist for KiCad.
I had built KiCad and launched it => non retina settings (OK, was not correctly
configured).
I changed the setting in Info.plist directly in the bundle and it nearly drove
me
On Oct 10, 2014, at 2:34 PM, Bernhard Stegmaier wrote:
> Well, it might seem so but that’s IMHO not the whole story.
>
> From an OSX perspective there currently is not “some apps”, it is just *one*
> application, the kicad launcher.
> Having the other (command-line) applications in the bundle i
On Oct 10, 2014, at 12:27 PM, Ian Woloschin wrote:
> Andy,
>
> I think that's the opposite of what I want! :)
>
> OS X is "smart" in that it tries to run the integrated graphics unless a
> specific application (or hardware feature, like an external monitor) requests
> discrete graphics. For
Well, it might seem so but that’s IMHO not the whole story.
>From an OSX perspective there currently is not “some apps”, it is just *one*
>application, the kicad launcher.
Having the other (command-line) applications in the bundle is just a workaround
and OSX doesn’t know anything about them fro
The current behavior is not acceptable in OS X.
The icons are mostly wrong.
I think it is because of the new bundling method.
Before, each app had the right icon attached to it. Now it is really confusing,
and very impractical as some apps have the wrong icon, and some other apps have
a sheet ico
Andy,
I think that's the opposite of what I want! :)
OS X is "smart" in that it tries to run the integrated graphics unless a
specific application (or hardware feature, like an external monitor)
requests discrete graphics. For example, launching KiCad doesn't require
discrete graphics, but when
On Oct 10, 2014, at 12:07 PM, Andy Peters wrote:
> On Oct 9, 2014, at 12:03 PM, Ian Woloschin wrote:
>
>> Easiest way to tell is using gfxCardStatus, https://gfx.io/, which will tell
>> you what's running. You can also, sort of, lock it to integrated or
>> discrete. I did a quick test and K
On Oct 9, 2014, at 12:03 PM, Ian Woloschin wrote:
> Easiest way to tell is using gfxCardStatus, https://gfx.io/, which will tell
> you what's running. You can also, sort of, lock it to integrated or
> discrete. I did a quick test and KiCad ran fine when locked to the
> integrated card, so I
That’s fine, I just wanted to know current/intended behavior.
It doesn’t seem to be possible to associate an extension in a way that only the
intended icon is shown.
It will stay as it is with regard to the main bundle then, i.e. only .pro files
are associated with it.
The other file types will
KiCad (the application launcher) is not design to open board or
schematic files. It merely opens the project file and launches the
appropriate application selected by the user. I don't think we would
want to launch pcbnew from kicad in the manner you described because
occasionally it is useful to
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
Hi Benoit,
Just expanding upon Wayne's answer, the way you would remove wxWidgets
2.8.12 development package on Ubuntu would be
sudo apt-get remove wxwidgets2.8-dev
or
sudo aptitude remove wxwidgets2.8-dev
I do not recommend modifying the CMake files to remove features. There are
command line
Add -DwxWidgits_CONFIG_EXECUTABLE=/path/to/the/correct/wx-config when
running cmake. Otherwise, the cmake module that finds wxWidgets will
find the first one it discovers which in you case is 2.8.12. The other
option it to remove the the wxWidgets 2.8.12 development package.
On 10/10/2014 11:34
In response to a message written on 10.10.2014 15:41, from Benoît Roehr:
> Hello guys,
>
> My problem with wxWidget 3.0 and CMake continues, I've tried to make this work
> for at least 10 hours now, and can't find any solution anywhere. I'm too noob
> with linux for the moment.
Comment out all „f
In response to a message written on 10.10.2014 17:34, from Benoît Roehr:
> Aw sorry everyone. I just noticed my previous mail was only sent to Brian.
> [...]
I think this list mechanism need to add field in header:
Reply-To: kicad-developers@lists.launchpad.net
kicad-users has it.
That should ends
Aw sorry everyone. I just noticed my previous mail was only sent to
Brian. It was a reply made in the build-under-windows subject. I join it
in this subject here:
On 09/10/2014 11:28, Brian Sidebotham wrote:
Lastly, if you do want to develop KiCad I would strongly urge moving
to Linux for devel
In response to a message written on 10.10.2014 15:49, from Nick Østergaard:
> Hello
>
> I just tried it on the sonde xilinx demo board with kicad and it
> worked there. Although I pulled the latest updated from your repo, I
> do not see the error in the terminal, but the text window inside your
>
Yes, I had to change the layer names in text editor for my old boards made
in old version of Kicad (French) to make them readable by the new 2014
builds.
The front and back copper layers where saved as "dessus.cu" and "dessous.cu"
and new kicad wasn't able to understand those.
On Fri, Oct 10, 2014
In response to a message written on 10.10.2014 13:38, from Wayne Stambaugh:
> These changes are only to make the UI strings consistent. Changing module to
> footprint in the board file would break the file format which is something I
> would be very reluctant to do.
BTW. Layer names nomenclature
Hello
I just tried it on the sonde xilinx demo board with kicad and it
worked there. Although I pulled the latest updated from your repo, I
do not see the error in the terminal, but the text window inside your
qui. I will send you the board to test with privately.
Nick
2014-10-10 13:03 GMT+02:00
Hello guys,
My problem with wxWidget 3.0 and CMake continues, I've tried to make
this work for at least 10 hours now, and can't find any solution
anywhere. I'm too noob with linux for the moment.
List of what I tried:
Installing latest wxWidget package (3.0.2)
Removing wx2.8
Remov
These changes are only to make the UI strings consistent. Changing
module to footprint in the board file would break the file format which
is something I would be very reluctant to do.
On 10/10/2014 4:37 AM, Kaspar Emanuel wrote:
> I guess all this renaming won't affect the s-expr file format rig
In response to a message written on 10.10.2014 03:34, from Adam Wolf:
> It is my guess that the issue isn't with the particular build, but instead
> something you didn't expect in the input file.
Input file is still parsed by kicad and python methods delivered by pcbnew.py
gives objects to my scri
I guess all this renaming won't affect the s-expr file format right? The
footprint files usually start with "(module".
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launc
29 matches
Mail list logo
