Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll

2020-12-11 Thread develop
<mailto:mark.ros...@gmail.com> @Mark Roszko: works now, thanks for your support! Von: Kicad-developers Im Auftrag von Mark Roszko Gesendet: 05 December 2020 20:29 An: Roberto Fernández Bautista Cc: KiCad Developers Betreff: Re: [Kicad-developers] MSVC compile: missing s3d_plugin_o

Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll

2020-12-05 Thread Mark Roszko
t;> Anything missing? >> >> >> >> >> >> *Von:* Mark Roszko >> *Gesendet:* 21 November 2020 14:01 >> *An:* deve...@worldinone.at >> *Cc:* KiCad Developers >> *Betreff:* Re: [Kicad-developers] MSVC compile: missing >> s3d_plugin_oce.dll >&

Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll

2020-12-02 Thread Roberto Fernández Bautista
ries as per the web documentation: > > boost cairo curl glew gettext glm icu ngspice opencascade opengl openssl > python3 wxwidgets zlib. > > Anything missing? > > > > > > *Von:* Mark Roszko > *Gesendet:* 21 November 2020 14:01 > *An:* deve...@worldinone.at > *Cc

Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll

2020-12-02 Thread jp charras
*An:* deve...@worldinone.at *Cc:* KiCad Developers *Betreff:* Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll If the kiface file exists in that path, the failure to load is because you are missing more dependencies in the install\bin folder that need to be copied from vcpkg debug

Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll

2020-12-01 Thread develop
wxwidgets zlib. Anything missing? Von: Mark Roszko Gesendet: 21 November 2020 14:01 An: deve...@worldinone.at Cc: KiCad Developers Betreff: Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll If the kiface file exists in that path, the failure to load is because you

Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll

2020-11-21 Thread Mark Roszko
gt; and I'm on wxwidgets 3.1.4. But one week or so ago, everything was ok. > Trouble started after upgrading vcpkg. > > -Martin > > > > *Von:* Mark Roszko > *Gesendet:* 16 November 2020 20:56 > *An:* deve...@worldinone.at > *Betreff:* Re: [Kicad-developers] MSVC compile:

Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll

2020-11-21 Thread develop
3.1.4. But one week or so ago, everything was ok. Trouble started after upgrading vcpkg. -Martin Von: Mark Roszko Gesendet: 16 November 2020 20:56 An: deve...@worldinone.at Betreff: Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll Probably a few weeks waitI have

Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll

2020-11-16 Thread Mark Roszko
Ah it's a bug in vcpkg I need to fix upstream. For now you'll need to include in your kicad install folder for debug, the non-debug versions of freetype, zlib, bz2 and libpng On Mon, Nov 16, 2020 at 1:44 PM Mark Roszko wrote: > Ah I've been meaning to fix that. There's something wrong with the

Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll

2020-11-16 Thread Mark Roszko
Ah I've been meaning to fix that. There's something wrong with the compilation settings and/or wxdynamiclibrary loader that's causing it not to load DLLs from the application's executable directory, very specifically for the OCE plugin. On Mon, Nov 16, 2020 at 6:22 AM wrote: > Compiling the

[Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll

2020-11-16 Thread develop
Compiling the current source (7043) with MSVC and the proposed CMakeSettings.json I get a missing s3d_plugin_oce.dll error when starting the 3D viewer. What is wrong here? -Martin. ___ Mailing list: https://launchpad.net/~kicad-developers Post to

Re: [Kicad-developers] MSVC build, incomplete version info

2020-11-15 Thread Ian McInerney
In order for the version string to contain the git version information, the build must be done inside a git repository. -Ian On Sun, Nov 15, 2020 at 6:36 PM wrote: > Thanks to Mark Roszko’s help I can build now with MSVC and KiCad runs ok. > > But then, the version info looks strange (see

[Kicad-developers] MSVC build, incomplete version info

2020-11-15 Thread develop
Thanks to Mark Roszko's help I can build now with MSVC and KiCad runs ok. But then, the version info looks strange (see below). I'm not pulling or branching, simply copying the source over. What am I missing? Application: KiCad Version: 5.99.0-unknown, debug build Libraries:

Re: [Kicad-developers] MSVC W10 build crashes in pcbnew : context already locked

2020-11-04 Thread Mark Roszko
Update to latest, there's a bad exception handler that causes the context already locked error. There was another bug that actually caused an exception. On Wed, Nov 4, 2020 at 2:11 AM wrote: > The current source (~7am UTC) crashes in pcbnew at opengl_gal.cpp(598) due > to “Context already

[Kicad-developers] MSVC W10 build crashes in pcbnew : context already locked

2020-11-03 Thread develop
The current source (~7am UTC) crashes in pcbnew at opengl_gal.cpp(598) due to "Context already locked". See attached log. > _pcbnew.kiface!KIGFX::OPENGL_GAL::lockContext(int aClientCookie) Zeile > 598 C++ _pcbnew.kiface!KIGFX::GAL_CONTEXT_LOCKER::GAL_CONTEXT_LOCKER(KIGFX::GAL

Re: [Kicad-developers] MSVC?

2019-06-28 Thread Wayne Stambaugh
Once the coding policy violations are fixed and the printf debugging statements are removed, I don't see any show stoppers. I have tested this to see if it breaks msys2 builds so hopefully it's already be tested for that. Cheers, Wayne On 6/27/19 6:02 AM, Simon Richter wrote: > Hi, > > I've

Re: [Kicad-developers] MSVC?

2019-06-27 Thread Tomasz Wlostowski
On 27/06/2019 12:02, Simon Richter wrote: > Hi, > > I've rebased[1] Tom's adaptation of my MSVC branch on top of current > master, seems to compile still[2], except for the usual dependency problems > with the generated lexers[3]. > > In this branch, we have an assembler based libcontext (taken

[Kicad-developers] MSVC?

2019-06-27 Thread Simon Richter
Hi, I've rebased[1] Tom's adaptation of my MSVC branch on top of current master, seems to compile still[2], except for the usual dependency problems with the generated lexers[3]. In this branch, we have an assembler based libcontext (taken over from boost) that is in a later commit replaced by