Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
build bot in the github, I see one nice project
ollydbg:
--- Quote from: Grit Clef on October 19, 2024, 01:29:10 pm ---Another common problem is:
--- Code: ---g++.exe -shared -L..\..\..\devel32 -LD:/msys64/opt/wxwidgets3.2/lib -LD:/msys64/opt/wxwidgets3.2/lib\gcc_dll ..\\..\\..\\.objs32\\plugins\\contrib\\DoxyBlocks\\DoxyBlocksLogger.o ..\\..\\..\\.objs32\\plugins\\contrib\\DoxyBlocks\\ExtractDocs.o ..\\..\\..\\.objs32\\plugins\\contrib\\DoxyBlocks\\AutoDoc.o ..\\..\\..\\.objs32\\plugins\\contrib\\DoxyBlocks\\DoxyBlocks.o
∧∧∧∧∧∧
..\\..\\..\\.objs32\\plugins\\contrib\\DoxyBlocks\\DoxyBlocks.o ..\\..\\..\\.objs32\\plugins\\contrib\\DoxyBlocks\\ConfigPanel.o ..\\..\\..\\.objs32\\plugins\\contrib\\DoxyBlocks\\Config.o -o ..\\..\\..\\devel32\\share\\CodeBlocks\\plugins\\DoxyBlocks.dll -Wl,--enable-auto-import -mthreads -lcodeblocks -lwxmsw32u
D:/msys64/opt/mingw32/bin/../lib/gcc/i686-w64-mingw32/14.2.0/../../../../i686-w64-mingw32/bin/ld.exe: ..\..\..\.objs32\plugins\contrib\DoxyBlocks\DoxyBlocks.o:DoxyBlocks.cpp:(.text+0x0): multiple definition of `DoxyBlocks::GetEventTable() const'; ..\..\..\.objs32\plugins\contrib\DoxyBlocks\DoxyBlocks.o:DoxyBlocks.cpp:(.text+0x0): first defined here
D:/msys64/opt/mingw32/bin/../lib/gcc/i686-w64-mingw32/14.2.0/../../../../i686-w64-mingw32/bin/ld.exe: ..\..\..\.objs32\plugins\contrib\DoxyBlocks\DoxyBlocks.o:DoxyBlocks.cpp:(.text+0x10): multiple definition of `DoxyBlocks::GetEventHashTable() const'; ..\..\..\.objs32\plugins\contrib\DoxyBlocks\DoxyBlocks.o:DoxyBlocks.cpp:(.text+0x10): first defined here
...........
--- End code ---
There are multiple same object files provided.
--- End quote ---
You mean there are 2 "DoxyBlocks.o" in the build options when linking?
I think the cb2make plugin should have some ways to remove those duplicated linking objects.
stahta01:
--- Quote from: stahta01 on October 19, 2024, 04:50:14 pm ---
--- Code: ---$ pacman -Qo /mingw64/bin/repstopdf.exe
/mingw64/bin/repstopdf.exe is owned by mingw-w64-x86_64-texlive-core 2023.20230404-1
--- End code ---
Some places use "repstopdf" instead of "epstopdf"
Edit: But, it did not work for me.
--- Code: ---C:\msys64\mingw64\bin\runscript.tlu:922: C:\msys64\mingw64\bin\runscript.tlu:853: no appropriate script or program found
: epstopdf
--- End code ---
${MINGW_PACKAGE_PREFIX}-ghostscript should have missing scripts.
But, I still could not find script
Tim S.
--- End quote ---
Got it.
--- Code: ---$ pacman -Qo /mingw64/bin/epstopdf.exe
/mingw64/bin/epstopdf.exe is owned by mingw-w64-x86_64-texlive-font-utils 2023.20230404-1
--- End code ---
Now this works
--- Code: ---$ epstopdf --version
epstopdf ($Id: epstopdf.pl 66407 2023-03-06 23:44:49Z karl $) 2.31
Copyright 2009-2023 Karl Berry et al.
Copyright 2002-2009 Gerben Wierda et al.
Copyright 1998-2001 Sebastian Rahtz et al.
License RBSD: Revised BSD <http://www.xfree86.org/3.3.6/COPYRIGHT2.html#5>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
--- End code ---
Tim S.
Grit Clef:
The first codeblocks build with partial plugins is out.
See https://github.com/zxunge/winstyle-codeblocks-bins/actions/runs/11418689815 .
ollydbg:
--- Quote from: Grit Clef on October 19, 2024, 06:33:07 pm ---The first codeblocks build with partial plugins is out.
See https://github.com/zxunge/winstyle-codeblocks-bins/actions/runs/11418689815 .
--- End quote ---
The latest one should be here: Update main.yml zxunge/winstyle-codeblocks-bins@c608334
There are two packages, which one is the final result zip file?
Why do you have a "update.exe" in your code repo?
Grit Clef:
codeblocks32_output.zip is the final; update.exe was converted from update.bat use an online tool, for use inside MSYS2 shell.(I first used winpty, but it just succeeded on my PC, failed on GitHub CI Server. So I tried that; although it was not perfect as the exe couldn't copy CbLauncher.exe to the output32 directory.)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version