The FindGLM script has been tested on OSX with Homebrew as well and is
reported
to work. Unless there are bugs introduced by the newer GLM versions I
think we
can safely apply the patch and everything should build OK once glm is
installed.
Although I set the glm version requirement to minimum
I have been chasing down a user bug on OS X, sorry. I have a stack of
patches to test though, and yours is on top :)
On Sun, Dec 6, 2015 at 2:43 PM, Mark Roszko wrote:
> Anyone get a chance to test on OSX?
>
> I really want to get this committed to devel before I go
On 12/6/2015 3:52 PM, Adam Wolf wrote:
> If it would help the installer, would it help if we ifdef OSX out, and I
> test on OS X next week and we remove the ifdef?
>
> I am also relatively comfortable applying this on OS X without testing
> it. I have been neck deep in that code over the last
On 4 December 2015 at 07:17, jp charras wrote:
> Le 04/12/2015 14:54, Wayne Stambaugh a écrit :
>> Thanks Henner. I'll take a look at it when I get a chance. I'm sure
>> this isn't the only place this pattern is used. If you have a patch,
>> please submit it.
>>
>>
When are you planning on doing the 4.0.1 release? Todayish or in about 7
days?
Adam Wolf
On Sun, Dec 6, 2015, 5:41 PM Wayne Stambaugh wrote:
> On 12/6/2015 3:52 PM, Adam Wolf wrote:
> > If it would help the installer, would it help if we ifdef OSX out, and I
> > test on
I am very tempted to just apply this to the 4.0.0 windows installer,
just such that the libs will actually work when people install them.
Should I refrain from this?
I have tested the patch on windows and linux. It works as expected.
2015-12-04 15:21 GMT+01:00 Wayne Stambaugh
On 31 July 2015 at 08:47, Wayne Stambaugh wrote:
> I'm confused, are we talking about the freerouting.net link or KiCad's
> internal autorouter? If the link to freerouting.net is still active, it
> should be removed from KiCad since it is no longer active. I thought
> this
I've written a FindGLM script to help with the effort to remove glm source
code from
the kicad tree. This works on Linux (well, at least Debian) but needs some
testing
on MSYS2 and OSX. I believe this script is necessary because:
1. Different distributions are erratic in the inclusion of a
Thanks Bernhard,
I just checked on MSYS2 and it works as well. Can someone push the
FindGLM.cmake script on
google drive into the kicad/CMakeModules directory? I'll create a branch
later and see if there are
any issues encountered when I delete the glm source from the tree and use
find_package +
The attached patch makes changes so that kicad uses an installed
GLM library rather than the glm source code currently in the kicad tree.
The FindGLM.cmake script included has been tested on Debian Linux,
MSYS2, and OSX+MacPorts.
This patch does not delete the include/gal/opengl/glm directory
Anyone get a chance to test on OSX?
I really want to get this committed to devel before I go doing more things :)
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe :
… works fine on OS X with a MacPorts installed glm:
bstegmaier$ cmake .
-- The CXX compiler identification is AppleClang 7.0.0.7000176
-- The C compiler identification is AppleClang 7.0.0.7000176
-- Check for working CXX compiler:
On 12/6/2015 3:48 PM, Nick Østergaard wrote:
> I am very tempted to just apply this to the 4.0.0 windows installer,
> just such that the libs will actually work when people install them.
>
> Should I refrain from this?
Please hold off. I would rather not have the windows 4.0.0 package use
I believe that there was integration done so that if you click the
autorouter button, it tells you in the status bar to put the jar in a
certain path, at which point the button works like it did before--actually,
a little better, because for some reason Java remembers the path and I
don't need to
The GLM stuff has been installed on the OS X build server. Let me know
when the first builds come through that should use it, and I will then have
someone on 10.7 test it. (That is the tricky part about dependencies on
the OS X build server, making sure they're compiled so crusty old systems
can
On 6 December 2015 at 20:58, Adam Wolf wrote:
> I believe that there was integration done so that if you click the
> autorouter button, it tells you in the status bar to put the jar in a
> certain path, at which point the button works like it did before--actually,
>
16 matches
Mail list logo