2015-01-29 2:40 GMT+03:00 Bob Gustafson :
> From the KiCad directory, I loaded a fresh source copy by:
>
>bzr checkout lp:kicad kicad.bzr
>
> (I use the checkout so I can enter the kicad.bzr and do ‘bzr up’ )
>
> Then enter the kicad.bzr directory and do:
>
>sh ../kicad-configure.sh 2>&1 |
From the KiCad directory, I loaded a fresh source copy by:
bzr checkout lp:kicad kicad.bzr
(I use the checkout so I can enter the kicad.bzr and do ‘bzr up’ )
Then enter the kicad.bzr directory and do:
sh ../kicad-configure.sh 2>&1 | tee config.out
The kicad-configure.sh file is attached
I'm building fresh from 5393. When it finishes I will post a summary.
Bob G
On 01/28/2015 04:24 PM, Adam Wolf wrote:
Yes.
On Jan 28, 2015 4:22 PM, "Nick Østergaard" mailto:oe.n...@gmail.com>> wrote:
Aren't a great deal of those from the boost build?
2015-01-28 23:21 GMT+01:00 Jean-P
I built the boost separately awhile ago 1_57_0
The messages seem to be various..
Bob G
On 01/28/2015 04:22 PM, Nick Østergaard wrote:
Aren't a great deal of those from the boost build?
2015-01-28 23:21 GMT+01:00 Jean-Paul Louis :
Adam,
I also get thousands of warnings when I build from scrat
But do you build boost also? I guess that those are not to be counted.
Also remember that warnings are not a single line usually.
2015-01-28 23:27 GMT+01:00 Bob Gustafson :
> In the output from my cmake config it is
>
> AppleClang 6.0.0.656
>
> I'm running latest macosx 10.10.2 and latest Xcod
In the output from my cmake config it is
AppleClang 6.0.0.656
I'm running latest macosx 10.10.2 and latest Xcode
I'm getting these on my Linux system too, but I haven't counted them
Bob G
On 01/28/2015 04:10 PM, Adam Wolf wrote:
Hi Bob,
What compiler are you using?
Adam Wolf
O
Yes.
On Jan 28, 2015 4:22 PM, "Nick Østergaard" wrote:
> Aren't a great deal of those from the boost build?
>
> 2015-01-28 23:21 GMT+01:00 Jean-Paul Louis :
> > Adam,
> > I also get thousands of warnings when I build from scratch from the
> launchpad repo (delete the whole kicad folder and the bu
Aren't a great deal of those from the boost build?
2015-01-28 23:21 GMT+01:00 Jean-Paul Louis :
> Adam,
> I also get thousands of warnings when I build from scratch from the launchpad
> repo (delete the whole kicad folder and the build folder).
>
> I compile with the latest version of clang.
> Mo
Adam,
I also get thousands of warnings when I build from scratch from the launchpad
repo (delete the whole kicad folder and the build folder).
I compile with the latest version of clang.
Most of those warnings relate to overloaded things. I will keep the log when I
rebuild.
Jean-Paul
AC9GH
>
Hi Bob,
What compiler are you using?
Adam Wolf
On Jan 28, 2015 4:08 PM, "Bob Gustafson" wrote:
> When I build kicad, I get a lot of warnings and 'notes' in the output
>
> ( output from:
> cd kicad.bzr
> make 2>&1 | tee kicad_make.out
> )
>
> At last count there are around 7654 warnings (add
When I build kicad, I get a lot of warnings and 'notes' in the output
( output from:
cd kicad.bzr
make 2>&1 | tee kicad_make.out
)
At last count there are around 7654 warnings (adding up the 'nnn
warnings generated' lines).
Is this normal? Is everyone seeing these messages?
Bob G
__
On 01/28/2015 01:45 AM, jp charras wrote:
Le 28/01/2015 08:07, Bernhard Stegmaier a écrit :
Again, I am open for all reasonable suggestions for the path itself, this is
not the discussion here.
The only thing I want to say is that the install prefix concept in my opinion
is just a unix thing
Hi folks,
>From a packaging perspective, and the perspective of getting this good code
Wayne wrote in the codebase, I say let's go with
GetOSXKicadMachineDataDir(). It matches the rest of the OS X work Bernhard
and I and everyone else have been doing for months and months.
All these search path
I tryied to build latest bzr, but no luck, problems with wx.
So I installed 5391 from js reynaud ppa, and problem solved.
sorry for the noise
regards,
yann
Le 28/01/2015 07:43, Nick Østergaard a écrit :
So you should try to build 5229 at least, probably no need to upgrade wx then.
2015-01-2
OK... then, for now just simply setting the base to a fixed/hardcoded
/Library/Application Support/kicad
will probably do the trick for OSX and at least should be consistent to
what we have at the moment spread over various spots in the code.
You could do that without any CMake magic directly i
On 1/28/2015 2:42 AM, Fat-Zer wrote:
> By the word, are there any arguments for using env vars rather than a
> configuration file to store the paths?
Cross platform path incompatibilities (fp-lib-table would not be cross
platform compatible with stored paths) and development purposes (allows
devel
On 1/28/2015 2:07 AM, Bernhard Stegmaier wrote:
> Again, I am open for all reasonable suggestions for the path itself, this is
> not the discussion here.
Correct. We've turned this discussion into way more than I had
intended. The discussion should be what is the best *default* path
(most commo
17 matches
Mail list logo
