Hi Ian,
On Wed, Aug 28, 2019 at 04:36:03PM +0200, Ian McInerney wrote:
> Just to be clear, I was only going to focus on cleaning up the static
> linkage in the current build process. While items in common could be moved
> into a new DLL, I don't have enough experience with that to try to attempt
Just to be clear, I was only going to focus on cleaning up the static
linkage in the current build process. While items in common could be moved
into a new DLL, I don't have enough experience with that to try to attempt
it right now.
-Ian
On Wed, Aug 28, 2019 at 4:31 PM Thomas Pointhuber
wrote:
Please go for it. The separate DLLs make it hard to design a python api
where eeschema and pcbnew can share resources.
Regards, Thomas
Am 28.08.19 um 16:03 schrieb Simon Richter:
> Hi,
>
> On Wed, Aug 28, 2019 at 10:47:52AM +0200, Ian McInerney wrote:
>
>> I think that the only way to really fi
Hi,
On Wed, Aug 28, 2019 at 10:47:52AM +0200, Ian McInerney wrote:
> I think that the only way to really fix this is to split common up into
> some smaller units,
I had the same idea already. This works for some parts (for example I was
able to split off dlist as an experiment), but the base_uni
Ian,
I'm guessing that getting rid of the circular build dependencies would
probably get rid of most if not all of these issues so I'm all for this.
Cheers,
Wayne
On 8/28/19 5:33 AM, Ian McInerney wrote:
> Correction, dxf2idf didn't need gal, it needed opengl as a dependency
> (which also wans'
Correction, dxf2idf didn't need gal, it needed opengl as a dependency
(which also wans't specified in the CMakeLists.txt file...). But now I will
still run into the circular dependency problem that John posted in that bug
report, so I still want to refactor the common library into smaller chunks.
Thanks for the pointers. After digging into this some more, I think what is
happening is that including the sanitizers changes the behavior of the
linker. It seems that it really doesn't like undefined symbols when linking
executables, even if there is no visible dependency path that leads to
them.
Hi,
On Tue, Aug 27, 2019 at 02:56:37AM +0200, Ian McInerney wrote:
> I was trying to do a fresh build of master with the address sanitizer
> enabled in Clang, and I am receiving a strange linker error, and was
> curious if anyone else had any thoughts on it.
I fixed a similar error on MSVC once.
I was trying to do a fresh build of master with the address sanitizer
enabled in Clang, and I am receiving a strange linker error, and was
curious if anyone else had any thoughts on it.
When it tries to link the eeschema executable, it throws an error
complaining about a missing Kiface symbol:
Sc
9 matches
Mail list logo
