kicad-developers team mailing list archive

[Mário Luzeiro <mrluzeiro@xxxxx>]

Hi Maurice, thanks for trying it !

Cirilo can give more details, but because of the 3D plugins, you have to build.. and install it.
I am testing in on Windows once in a while, building it on a MSYS2
I run 'make install -j4'
and run kicad

I got help on IRC from nickoe (thanks!) on setup and running this on Windows and Linux.

On linux I am using the following:
make DESTDIR=/tmp/kicad install -j7
LD_LIBRARY_PATH=/tmp/kicad/usr/local/lib:$LD_LIBRARY_PATH /tmp/kicad/usr/local/bin/pcbnew

but on windows MSYS2 this is not need for me...

Mario Luzeiro

________________________________________
From: Kicad-developers [kicad-developers-bounces+mrluzeiro=ua.pt@xxxxxxxxxxxxxxxxxxx] on behalf of easyw [easyw@xxxxxxxxxxxx]
Sent: 16 February 2016 22:26
To: Cirilo Bernardo
Cc: KiCad Developers
Subject: Re: [Kicad-developers] 3D refactor 3D model path: dropped env vars?

Hi Cirilo and Mario,
thank you for your reply ...
I'm testing the new 3D refactoring, built from this repo
https://code.launchpad.net/~mrluzeiro/kicad/kicad_new3d-viewer
in windows 8/64b
what I'm experiencing is that I cannot display any 3D model at all...
I tried also with an absolute path, and I also don't have any model
displayed on the preview...
I can see the board and tracks in 3d-viewer both on OpenGL and in
Raytracing, but nope for 3D models ...
Is there anyone that has tested that in windows?
If I build the standard bzr6558 everything goes fine

thank you for feedback
Maurice


On 16/02/2016 22.43, Cirilo Bernardo wrote:
> Hi Maurice,
>
>   For legacy support ${KISYS3DMOD} is magically and invisibly supported
> by the filename resolver. The resolver will also correctly resolve any
> path specified like ${ENV_VAR}/some/path.  However, once the new 3D
> plugin code is merged I would discourage any future use of ${KISYS3DMOD}
> and ${KIPRJMOD} in the names of files - these will still work but in my
> opinion is a bad habit and will work against the filename resolver's
> concept to eliminate environment variables in filename resolution and to
> use a configurable text file to store root paths instead.
>
>   The ${KIPRJMOD} in fact does not need to be specified at all and can
> be completely removed from names. By default the filename resolver will
> attempt to resolve partial paths by checking in the current project
> directory first. This was done as part of the plan to ensure better
> portability of a project directory.
>
> - Cirilo
>
>
> On Wed, Feb 17, 2016 at 6:46 AM, easyw <easyw@xxxxxxxxxxxx
> <mailto:easyw@xxxxxxxxxxxx>> wrote:
>
>     have the environment variables
>     ${KIPRJMOD}
>     ${KISYS3DMOD}
>     been dropped by the new 3D refactoring?
>
>     _______________________________________________
>     Mailing list: https://launchpad.net/~kicad-developers
>     Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>     <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>     Unsubscribe : https://launchpad.net/~kicad-developers
>     More help   : https://help.launchpad.net/ListHelp
>
>

_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp