Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll
<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_oce.dll The latest vcpkg master should have opencascade's linkage to debug freetype libraries fixed now. You will have to git pull --rebase your vcpkg folder. Run .\vcpkg upgrade --no-dry-run and then once rebuilt, copy the DLLs all over again to the kicad install bin On Wed, Dec 2, 2020 at 9:58 AM Roberto Fernández Bautista mailto:roberto.fer@gmail.com> > wrote: Just one thing to check: Are you running the "install" target through visual studio? Note that for each executable you can either install it and debug or debug standalone I've fallen under the mistake before of debugging without installing and then wondering why I am getting error messages of dlls missing. On Wed, 2 Dec 2020 at 08:11, mailto:deve...@worldinone.at> > wrote: I copied over ALL of the dlls, just in case, and it did not help. If it is about dependencies, maybe I missed to install something in vcpkg. I installed the recommended libraries as per the web documentation: boost cairo curl glew gettext glm icu ngspice opencascade opengl openssl python3 wxwidgets zlib. Anything missing? Von: Mark Roszko mailto:mark.ros...@gmail.com> > Gesendet: 21 November 2020 14:01 An: deve...@worldinone.at <mailto:deve...@worldinone.at> Cc: KiCad Developers mailto:kicad-developers@lists.launchpad.net> > 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\bin or bin. On Sat, Nov 21, 2020 at 3:00 AM mailto:deve...@worldinone.at> > wrote: I got it sorted out, partially. After copying the right jpeg62.dll and lzmad.dll to the install directory for debug, KiCad started all right. When starting eeschema or pcbnew or anything loaded by kiway.cpp, I get an error about failing *.kiface to load. Debugging showed that in wxDynamicLibrary::Load, RawLoad is called with the correct path (in my case but that returns NULL, as it fails to load the library. Unfortunately, RawLoad does not provide any error codes. Is this the bug you mentioned? But then, the path passed to RawLoad is correct, so I do not see what can be wrong here. Other modules like ntdll, comctrl32 e.a. are loaded ok. Only thing I can image is that – out of the blue - there’s a problem with the path string. Is it a MSVC specific thing (the nightlies obviously are built all right)? Ok, the nightlies are built with wxwidgets 3.0.5 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 mailto:mark.ros...@gmail.com> > Gesendet: 16 November 2020 20:56 An: deve...@worldinone.at <mailto:deve...@worldinone.at> Betreff: Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll Probably a few weeks waitI have it on my queue to revisit vcpkg at some point and upstream also takes time to merge fixes. It's just easier to copy the DLLs like I noted. On Mon, Nov 16, 2020 at 2:45 PM mailto:deve...@worldinone.at> > wrote: Ok. Can you notify me when it’s fixed? Thanks a lot! -Martin Von: Mark Roszko mailto:mark.ros...@gmail.com> > Gesendet: Montag, 16. November 2020 20:14 An: deve...@worldinone.at <mailto:deve...@worldinone.at> Cc: KiCad Developers mailto:kicad-developers@lists.launchpad.net> > Betreff: Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll 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 mailto:mark.ros...@gmail.com> > wrote: 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 mailto:deve...@worldinone.at> > wrote: 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 : kicad-developers@lists.launchpad.net <mailto:kicad-developers@lists.launchpad.net> Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp -- Mark
Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll
The latest vcpkg master should have opencascade's linkage to debug freetype libraries fixed now. You will have to git pull --rebase your vcpkg folder. Run .\vcpkg upgrade --no-dry-run and then once rebuilt, copy the DLLs all over again to the kicad install bin On Wed, Dec 2, 2020 at 9:58 AM Roberto Fernández Bautista < roberto.fer@gmail.com> wrote: > Just one thing to check: Are you running the "install" target through > visual studio? Note that for each executable you can either install it and > debug or debug standalone > [image: image.png] > [image: image.png] > > I've fallen under the mistake before of debugging without installing and > then wondering why I am getting error messages of dlls missing. > > > On Wed, 2 Dec 2020 at 08:11, wrote: > >> I copied over ALL of the dlls, just in case, and it did not help. If it >> is about dependencies, maybe I missed to install something in vcpkg. I >> installed the recommended libraries 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:* 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\bin or bin. >> >> >> >> >> >> On Sat, Nov 21, 2020 at 3:00 AM wrote: >> >> I got it sorted out, partially. After copying the right jpeg62.dll and >> lzmad.dll to the install directory for debug, KiCad started all right. >> >> When starting eeschema or pcbnew or anything loaded by kiway.cpp, I get >> an error about failing *.kiface to load. >> >> Debugging showed that in wxDynamicLibrary::Load, RawLoad is called with >> the correct path (in my case >> >> >> but that returns NULL, as it fails to load the library. Unfortunately, >> RawLoad does not provide any error codes. >> >> Is this the bug you mentioned? But then, the path passed to RawLoad is >> correct, so I do not see what can be wrong here. Other modules like ntdll, >> comctrl32 e.a. are loaded ok. >> >> Only thing I can image is that – out of the blue - there’s a problem with >> the path string. Is it a MSVC specific thing (the nightlies obviously are >> built all right)? Ok, the nightlies are built with wxwidgets 3.0.5 >> >> 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: missing >> s3d_plugin_oce.dll >> >> >> >> Probably a few weeks wait....I have it on my queue to revisit vcpkg at >> some point and upstream also takes time to merge fixes. >> >> >> >> It's just easier to copy the DLLs like I noted. >> >> >> >> On Mon, Nov 16, 2020 at 2:45 PM wrote: >> >> Ok. Can you notify me when it’s fixed? Thanks a lot! >> >> -Martin >> >> >> >> *Von:* Mark Roszko >> *Gesendet:* Montag, 16. November 2020 20:14 >> *An:* deve...@worldinone.at >> *Cc:* KiCad Developers >> *Betreff:* Re: [Kicad-developers] MSVC compile: missing >> s3d_plugin_oce.dll >> >> >> >> 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 >> 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 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. >> >>
Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll
Just one thing to check: Are you running the "install" target through visual studio? Note that for each executable you can either install it and debug or debug standalone [image: image.png] [image: image.png] I've fallen under the mistake before of debugging without installing and then wondering why I am getting error messages of dlls missing. On Wed, 2 Dec 2020 at 08:11, wrote: > I copied over ALL of the dlls, just in case, and it did not help. If it is > about dependencies, maybe I missed to install something in vcpkg. I > installed the recommended libraries 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:* 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\bin or bin. > > > > > > On Sat, Nov 21, 2020 at 3:00 AM wrote: > > I got it sorted out, partially. After copying the right jpeg62.dll and > lzmad.dll to the install directory for debug, KiCad started all right. > > When starting eeschema or pcbnew or anything loaded by kiway.cpp, I get an > error about failing *.kiface to load. > > Debugging showed that in wxDynamicLibrary::Load, RawLoad is called with > the correct path (in my case > > > but that returns NULL, as it fails to load the library. Unfortunately, > RawLoad does not provide any error codes. > > Is this the bug you mentioned? But then, the path passed to RawLoad is > correct, so I do not see what can be wrong here. Other modules like ntdll, > comctrl32 e.a. are loaded ok. > > Only thing I can image is that – out of the blue - there’s a problem with > the path string. Is it a MSVC specific thing (the nightlies obviously are > built all right)? Ok, the nightlies are built with wxwidgets 3.0.5 > > 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: missing s3d_plugin_oce.dll > > > > Probably a few weeks waitI have it on my queue to revisit vcpkg at > some point and upstream also takes time to merge fixes. > > > > It's just easier to copy the DLLs like I noted. > > > > On Mon, Nov 16, 2020 at 2:45 PM wrote: > > Ok. Can you notify me when it’s fixed? Thanks a lot! > > -Martin > > > > *Von:* Mark Roszko > *Gesendet:* Montag, 16. November 2020 20:14 > *An:* deve...@worldinone.at > *Cc:* KiCad Developers > *Betreff:* Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll > > > > 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 > 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 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 : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > > > > > -- > > Mark > > > > > -- > > Mark > > > > > -- > > Mark > > > > > -- > > Mark > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll
Le 02/12/2020 à 08:15, deve...@worldinone.at a écrit :
I copied over ALL of the dlls, just in case, and it did not help. If
it is about dependencies, maybe I missed to install something in
vcpkg. I installed the recommended libraries as per the web documentation:
boost cairo curl glew gettext glm icu ngspice opencascade opengl
openssl python3 wxwidgets zlib.
Anything missing?
3d_plugin_oce.dll should be built by the kicad build process (as long as
you have enabled OCE or OCC)
It should be copied to kicad/bin/plugins/3d
*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 are missing more dependencies in the install\bin folder that need
to be copied from vcpkg debug\bin or bin.
On Sat, Nov 21, 2020 at 3:00 AM <mailto:deve...@worldinone.at>> wrote:
I got it sorted out, partially. After copying the right jpeg62.dll
and lzmad.dll to the install directory for debug, KiCad started
all right.
When starting eeschema or pcbnew or anything loaded by kiway.cpp,
I get an error about failing *.kiface to load.
Debugging showed that in wxDynamicLibrary::Load, RawLoad is called
with the correct path (in my case
but that returns NULL, as it fails to load the library.
Unfortunately, RawLoad does not provide any error codes.
Is this the bug you mentioned? But then, the path passed to
RawLoad is correct, so I do not see what can be wrong here. Other
modules like ntdll, comctrl32 e.a. are loaded ok.
Only thing I can image is that – out of the blue - there’s a
problem with the path string. Is it a MSVC specific thing (the
nightlies obviously are built all right)? Ok, the nightlies are
built with wxwidgets 3.0.5
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 mailto:mark.ros...@gmail.com>>
*Gesendet:* 16 November 2020 20:56
*An:* deve...@worldinone.at <mailto:deve...@worldinone.at>
*Betreff:* Re: [Kicad-developers] MSVC compile: missing
s3d_plugin_oce.dll
Probably a few weeks waitI have it on my queue to revisit
vcpkg at some point and upstream also takes time to merge fixes.
It's just easier to copy the DLLs like I noted.
On Mon, Nov 16, 2020 at 2:45 PM mailto:deve...@worldinone.at>> wrote:
Ok. Can you notify me when it’s fixed? Thanks a lot!
-Martin
*Von:*Mark Roszko mailto:mark.ros...@gmail.com>>
*Gesendet:* Montag, 16. November 2020 20:14
*An:* deve...@worldinone.at <mailto:deve...@worldinone.at>
*Cc:* KiCad Developers mailto:kicad-developers@lists.launchpad.net>>
*Betreff:* Re: [Kicad-developers] MSVC compile: missing
s3d_plugin_oce.dll
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
mailto:mark.ros...@gmail.com>> wrote:
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 mailto:deve...@worldinone.at>> wrote:
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
<https://launchpad.net/~kicad-developers>
Post to : kicad-developers@lists.launchpad.net
<mailto:kicad-developers@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/~kicad-developers>
More help : https://help.launchpad.net/ListHelp
<https://help.launchpad.net/ListHelp>
--
Mark
--
Mark
--
Mark
--
Mark
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
--
Jean-Pierre CHARRAS
_
Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll
I copied over ALL of the dlls, just in case, and it did not help. If it is about dependencies, maybe I missed to install something in vcpkg. I installed the recommended libraries 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: 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\bin or bin. On Sat, Nov 21, 2020 at 3:00 AM mailto:deve...@worldinone.at> > wrote: I got it sorted out, partially. After copying the right jpeg62.dll and lzmad.dll to the install directory for debug, KiCad started all right. When starting eeschema or pcbnew or anything loaded by kiway.cpp, I get an error about failing *.kiface to load. Debugging showed that in wxDynamicLibrary::Load, RawLoad is called with the correct path (in my case but that returns NULL, as it fails to load the library. Unfortunately, RawLoad does not provide any error codes. Is this the bug you mentioned? But then, the path passed to RawLoad is correct, so I do not see what can be wrong here. Other modules like ntdll, comctrl32 e.a. are loaded ok. Only thing I can image is that – out of the blue - there’s a problem with the path string. Is it a MSVC specific thing (the nightlies obviously are built all right)? Ok, the nightlies are built with wxwidgets 3.0.5 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 mailto:mark.ros...@gmail.com> > Gesendet: 16 November 2020 20:56 An: deve...@worldinone.at <mailto:deve...@worldinone.at> Betreff: Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll Probably a few weeks waitI have it on my queue to revisit vcpkg at some point and upstream also takes time to merge fixes. It's just easier to copy the DLLs like I noted. On Mon, Nov 16, 2020 at 2:45 PM mailto:deve...@worldinone.at> > wrote: Ok. Can you notify me when it’s fixed? Thanks a lot! -Martin Von: Mark Roszko mailto:mark.ros...@gmail.com> > Gesendet: Montag, 16. November 2020 20:14 An: deve...@worldinone.at <mailto:deve...@worldinone.at> Cc: KiCad Developers mailto:kicad-developers@lists.launchpad.net> > Betreff: Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll 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 mailto:mark.ros...@gmail.com> > wrote: 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 mailto:deve...@worldinone.at> > wrote: 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 : kicad-developers@lists.launchpad.net <mailto:kicad-developers@lists.launchpad.net> Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp -- Mark -- Mark -- Mark -- Mark ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
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\bin or bin. On Sat, Nov 21, 2020 at 3:00 AM wrote: > I got it sorted out, partially. After copying the right jpeg62.dll and > lzmad.dll to the install directory for debug, KiCad started all right. > > When starting eeschema or pcbnew or anything loaded by kiway.cpp, I get an > error about failing *.kiface to load. > > Debugging showed that in wxDynamicLibrary::Load, RawLoad is called with > the correct path (in my case > > > but that returns NULL, as it fails to load the library. Unfortunately, > RawLoad does not provide any error codes. > > Is this the bug you mentioned? But then, the path passed to RawLoad is > correct, so I do not see what can be wrong here. Other modules like ntdll, > comctrl32 e.a. are loaded ok. > > Only thing I can image is that – out of the blue - there’s a problem with > the path string. Is it a MSVC specific thing (the nightlies obviously are > built all right)? Ok, the nightlies are built with wxwidgets 3.0.5 > > 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: missing s3d_plugin_oce.dll > > > > Probably a few weeks waitI have it on my queue to revisit vcpkg at > some point and upstream also takes time to merge fixes. > > > > It's just easier to copy the DLLs like I noted. > > > > On Mon, Nov 16, 2020 at 2:45 PM wrote: > > Ok. Can you notify me when it’s fixed? Thanks a lot! > > -Martin > > > > *Von:* Mark Roszko > *Gesendet:* Montag, 16. November 2020 20:14 > *An:* deve...@worldinone.at > *Cc:* KiCad Developers > *Betreff:* Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll > > > > 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 > 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 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 : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > > > > > -- > > Mark > > > > > -- > > Mark > > > > > -- > > Mark > -- Mark ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll
I got it sorted out, partially. After copying the right jpeg62.dll and lzmad.dll to the install directory for debug, KiCad started all right. When starting eeschema or pcbnew or anything loaded by kiway.cpp, I get an error about failing *.kiface to load. Debugging showed that in wxDynamicLibrary::Load, RawLoad is called with the correct path (in my case but that returns NULL, as it fails to load the library. Unfortunately, RawLoad does not provide any error codes. Is this the bug you mentioned? But then, the path passed to RawLoad is correct, so I do not see what can be wrong here. Other modules like ntdll, comctrl32 e.a. are loaded ok. Only thing I can image is that – out of the blue - there’s a problem with the path string. Is it a MSVC specific thing (the nightlies obviously are built all right)? Ok, the nightlies are built with wxwidgets 3.0.5 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: missing s3d_plugin_oce.dll Probably a few weeks waitI have it on my queue to revisit vcpkg at some point and upstream also takes time to merge fixes. It's just easier to copy the DLLs like I noted. On Mon, Nov 16, 2020 at 2:45 PM mailto:deve...@worldinone.at> > wrote: Ok. Can you notify me when it’s fixed? Thanks a lot! -Martin Von: Mark Roszko mailto:mark.ros...@gmail.com> > Gesendet: Montag, 16. November 2020 20:14 An: deve...@worldinone.at <mailto:deve...@worldinone.at> Cc: KiCad Developers mailto:kicad-developers@lists.launchpad.net> > Betreff: Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll 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 mailto:mark.ros...@gmail.com> > wrote: 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 mailto:deve...@worldinone.at> > wrote: 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 : kicad-developers@lists.launchpad.net <mailto:kicad-developers@lists.launchpad.net> Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp -- Mark -- Mark -- Mark ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll
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 > 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 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 : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > > > -- > Mark > -- Mark ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll
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 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 : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- Mark ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll
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 : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] MSVC build, incomplete version info
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 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: > > wxWidgets 3.1.4 > > libcurl/7.73.0-DEV Schannel zlib/1.2.11 > > > > Platform: Windows 10 (build 19041), 64-bit edition, 64 bit, Little endian, > wxMSW > > > > Build Info: > > Date: Nov 15 2020 19:13:58 > > wxWidgets: 3.1.4 (wchar_t,STL containers) > > Boost: 1.73.0 > > OCC: 7.4.0 > > Curl: 7.73.0-DEV > > ngspice: 32 > > Compiler: Visual C++ 1928 without C++ ABI > > > > Build settings: > > KICAD_SCRIPTING=OFF > > KICAD_SCRIPTING_MODULES=OFF > > KICAD_SCRIPTING_PYTHON3=OFF > > KICAD_SCRIPTING_WXPYTHON=OFF > > KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF > > KICAD_SCRIPTING_ACTION_MENU=OFF > > KICAD_USE_OCC=ON > > KICAD_SPICE=ON > > KICAD_STDLIB_DEBUG=OFF > > KICAD_STDLIB_LIGHT_DEBUG=OFF > > KICAD_SANITIZE=OFF > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] MSVC build, incomplete version info
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: wxWidgets 3.1.4 libcurl/7.73.0-DEV Schannel zlib/1.2.11 Platform: Windows 10 (build 19041), 64-bit edition, 64 bit, Little endian, wxMSW Build Info: Date: Nov 15 2020 19:13:58 wxWidgets: 3.1.4 (wchar_t,STL containers) Boost: 1.73.0 OCC: 7.4.0 Curl: 7.73.0-DEV ngspice: 32 Compiler: Visual C++ 1928 without C++ ABI Build settings: KICAD_SCRIPTING=OFF KICAD_SCRIPTING_MODULES=OFF KICAD_SCRIPTING_PYTHON3=OFF KICAD_SCRIPTING_WXPYTHON=OFF KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF KICAD_SCRIPTING_ACTION_MENU=OFF KICAD_USE_OCC=ON KICAD_SPICE=ON KICAD_STDLIB_DEBUG=OFF KICAD_STDLIB_LIGHT_DEBUG=OFF KICAD_SANITIZE=OFF ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] MSVC W10 build crashes in pcbnew : context already locked
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 locked”. > > See attached log. > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- Mark ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] MSVC W10 build crashes in pcbnew : context already locked
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 * aGal) Zeile 1159 C++ _pcbnew.kiface!KIGFX::GAL_UPDATE_CONTEXT::GAL_UPDATE_CONTEXT(KIGFX::GAL * aGal) Zeile 1176 C++ _pcbnew.kiface!KIGFX::VIEW::UpdateItems() Zeile 1398C++ _pcbnew.kiface!EDA_DRAW_PANEL_GAL::DoRePaint() Zeile 196C++ _pcbnew.kiface!EDA_DRAW_PANEL_GAL::onRefreshTimer(wxTimerEvent & aEvent) Zeile 568 C++ wxbase314ud_vc_custom.dll!wxAppConsoleBase::HandleEvent(wxEvtHandler * handler, void(wxEvtHandler::*)(wxEvent &) func, wxEvent & event) Zeile 658 C++ wxbase314ud_vc_custom.dll!wxAppConsoleBase::CallEventHandler(wxEvtHandler * handler, wxEventFunctor & functor, wxEvent & event) Zeile 669 C++ wxbase314ud_vc_custom.dll!wxEvtHandler::ProcessEventIfMatchesId(const wxEventTableEntryBase & entry, wxEvtHandler * handler, wxEvent & event) Zeile 1426C++ wxbase314ud_vc_custom.dll!wxEvtHandler::SearchDynamicEventTable(wxEvent & event) Zeile 1897 C++ wxbase314ud_vc_custom.dll!wxEvtHandler::TryHereOnly(wxEvent & event) Zeile 1618 C++ wxbase314ud_vc_custom.dll!wxEvtHandler::TryBeforeAndHere(wxEvent & event) Zeile 3927C++ wxbase314ud_vc_custom.dll!wxEvtHandler::ProcessEventLocally(wxEvent & event) Zeile 1555 C++ wxbase314ud_vc_custom.dll!wxEvtHandler::ProcessEvent(wxEvent & event) Zeile 1528C++ wxbase314ud_vc_custom.dll!wxEvtHandler::SafelyProcessEvent(wxEvent & event) Zeile 1646 C++ wxbase314ud_vc_custom.dll!wxTimerImpl::SendEvent() Zeile 51 C++ wxbase314ud_vc_custom.dll!wxTimer::Notify() Zeile 109 C++ wxbase314ud_vc_custom.dll!wxTimerImpl::Notify() Zeile 47C++ wxbase314ud_vc_custom.dll!wxProcessTimer(wxMSWTimerImpl & timer) Zeile 161 C++ wxbase314ud_vc_custom.dll!wxTimerWndProc(HWND__ * hWnd, unsigned int message, unsigned __int64 wParam, __int64 lParam) Zeile 175C++ [Externer Code] _pcbnew.kiface!D_PAD::IsOnLayer(PCB_LAYER_ID aLayer) Zeile 551 C++ _pcbnew.kiface!KIGFX::PCB_RENDER_SETTINGS::GetColor(const KIGFX::VIEW_ITEM * aItem, int aLayer) Zeile 330 C++ _pcbnew.kiface!KIGFX::PCB_PAINTER::draw(const D_PAD * aPad, int aLayer) Zeile 879 C++ _pcbnew.kiface!KIGFX::PCB_PAINTER::Draw(const KIGFX::VIEW_ITEM * aItem, int aLayer) Zeile 421 C++ _pcbnew.kiface!KIGFX::VIEW::updateItemGeometry(KIGFX::VIEW_ITEM * aItem, int aLayer) Zeile 1293 C++ _pcbnew.kiface!KIGFX::VIEW::invalidateItem(KIGFX::VIEW_ITEM * aItem, int aUpdateFlags) Zeile 1223 C++ _pcbnew.kiface!KIGFX::VIEW::UpdateItems() Zeile 1410C++ _pcbnew.kiface!PCB_DRAW_PANEL_GAL::OnShow() Zeile 458 C++ _pcbnew.kiface!EDA_DRAW_PANEL_GAL::onShowTimer(wxTimerEvent & aEvent) Zeile 578 C++ wxbase314ud_vc_custom.dll!wxAppConsoleBase::HandleEvent(wxEvtHandler * handler, void(wxEvtHandler::*)(wxEvent &) func, wxEvent & event) Zeile 658 C++ wxbase314ud_vc_custom.dll!wxAppConsoleBase::CallEventHandler(wxEvtHandler * handler, wxEventFunctor & functor, wxEvent & event) Zeile 669 C++ wxbase314ud_vc_custom.dll!wxEvtHandler::ProcessEventIfMatchesId(const wxEventTableEntryBase & entry, wxEvtHandler * handler, wxEvent & event) Zeile 1426C++ wxbase314ud_vc_custom.dll!wxEvtHandler::SearchDynamicEventTable(wxEvent & event) Zeile 1897 C++ wxbase314ud_vc_custom.dll!wxEvtHandler::TryHereOnly(wxEvent & event) Zeile 1618 C++ wxbase314ud_vc_custom.dll!wxEvtHandler::TryBeforeAndHere(wxEvent & event) Zeile 3927C++ wxbase314ud_vc_custom.dll!wxEvtHandler::ProcessEventLocally(wxEvent & event) Zeile 1555 C++ wxbase314ud_vc_custom.dll!wxEvtHandler::ProcessEvent(wxEvent & event) Zeile 1528C++ wxbase314ud_vc_custom.dll!wxEvtHandler::SafelyProcessEvent(wxEvent & event) Zeile 1646 C++ wxbase314ud_vc_custom.dll!wxTimerImpl::SendEvent() Zeile 51 C++ wxbase314ud_vc_custom.dll!wxTimer::Notify() Zeile 109 C++ wxbase314ud_vc_custom.dll!wxTimerImpl::Notify() Zeile 47C++ wxbase314ud_vc_custom.dll!wxProcessTimer(wxMSWTimerImpl & timer) Zeile 161 C++ wxbase314ud_vc_custom.dll!wxTimerWndProc(HWND__ * hWnd, unsigned int message, unsigned __int64 wParam, __int64 lParam) Zeile 175C++ [Externer Code] wxmsw314ud_core_vc_custom.dll!wxGUIEventLoop::PreProcessMessage(tagMSG * msg) Zeile 96 C++ wxmsw314ud_core_vc_custom.dll!wxGUIEventLoop::ProcessMessage(tagMSG * msg) Zeile 163C++ wxmsw314ud_core_vc_custom.dll!wxGUIEventLoop::Dispatch()
Re: [Kicad-developers] MSVC?
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 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 Windows Fibers. > > Before I do any further work on this branch: which implementation should we > go with, so I can squash the branch to that state? > > I'd then do some more test builds and also actually run the program once or > twice, so we can get the branch ready for merging. > >Simon > > [1] https://git.launchpad.net/~sjr/kicad/msvc-new > [2] https://jenkins.simonrichter.eu/job/windows-kicad-msvc-tom/8/ > [3] https://jenkins.simonrichter.eu/job/windows-kicad-msvc-tom/9/ > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] MSVC?
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 over from > boost) that is in a later commit replaced by Windows Fibers. > > Before I do any further work on this branch: which implementation should we > go with, so I can squash the branch to that state? > Hi Simon, Thanks for your work. I'd go for the WinFiber API, it's stable, it's been in WinNT systems for ages... The libcontext backend for winfibers is somewhat ugly (it's just a proof of concept), would you be able to clean it up a bit before merging? Cheers, Tom ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] MSVC?
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 Windows Fibers. Before I do any further work on this branch: which implementation should we go with, so I can squash the branch to that state? I'd then do some more test builds and also actually run the program once or twice, so we can get the branch ready for merging. Simon [1] https://git.launchpad.net/~sjr/kicad/msvc-new [2] https://jenkins.simonrichter.eu/job/windows-kicad-msvc-tom/8/ [3] https://jenkins.simonrichter.eu/job/windows-kicad-msvc-tom/9/ ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
