Recent Posts

81

Development / Re: build bot in the github, I see one nice project

« Last post by ollydbg on September 25, 2024, 12:43:43 am »

When I looked at the link

[MinGW] make check problem Issue #9115 protocolbuffers/protobuf

or

Make commands not working on Windows 10 at setting check up Issue #297 libcheck/check

It looks like the "DLL_EXPORT" is predefined in the auto configure tool?


EDIT:

I will try this patch below in the github action.

Code

diff --git a/src/include/cbplugin.h b/src/include/cbplugin.h
index 10258e5..a3ce67b 100644
--- a/src/include/cbplugin.h
+++ b/src/include/cbplugin.h
@@ -23,11 +23,11 @@
         #ifdef EXPORT_LIB
             #define PLUGIN_EXPORT __declspec (dllexport)
         #else // !EXPORT_LIB
-            #ifdef BUILDING_PLUGIN
+            #if defined(BUILDING_PLUGIN) || defined(DLL_EXPORT)
                 #define PLUGIN_EXPORT __declspec (dllexport)
-            #else // !BUILDING_PLUGIN
+            #else // !BUILDING_PLUGIN && !DLL_EXPORT
                 #define PLUGIN_EXPORT __declspec (dllimport)
-            #endif // BUILDING_PLUGIN
+            #endif // BUILDING_PLUGIN || DLL_EXPORT
         #endif // EXPORT_LIB
     #endif // PLUGIN_EXPORT
 #else

Some good news, the above mentioned change works. 


Another issue/question is that why you need such patch:

https://github.com/asmwarrior/x86-codeblocks-builds/blob/main/0001-fix-32-bit-build-and-wxSmith.patch

?


I looked at this link:

https://github.com/msys2/MINGW-packages/tree/master/mingw-w64-codeblocks

I don't see they need such patch as yours.

82

Development / Re: build bot in the github, I see one nice project

« Last post by ollydbg on September 24, 2024, 04:54:24 pm »

Oh, when I tried your command:
The result is, first 13571 came out and then an error:
Error: Process completed with exit code 141.

The method already works in my fork, see here:

my fork's main branch

83

Development / Re: build bot in the github, I see one nice project

« Last post by Grit Clef on September 24, 2024, 04:39:28 pm »

Oh, when I tried your command:
The result is, first 13571 came out and then an error:
Error: Process completed with exit code 141.

84

Using Code::Blocks / Re: Update of documentation CB on Windows

« Last post by ollydbg on September 24, 2024, 04:32:53 pm »

Hi,

Just to illustrate and "for fun", an example of CB project with 64 generations of target on W11 64b, with same C source code (32 and 64 bit, Debug / Release, all declination of "free" compilers C/C++ available on Windows)
If you can configure correctly one compiler C/C++ into CB, then you can configure many...

And, to illustrated also, an example of target DLL in CB project with all of these compilers, two test program with call DLL "implicit" or "explicit" also in CB project, and finally test program in Python (not in CB, but maybe possible) here :
    https://github.com/tdechaize/Test_DLL_ALL

Very very open and simply IDE. Enjoy.

TDE.

Nice work!

Thanks for sharing the experience, especially so many kinds of compilers. 

85

Development / Re: build bot in the github, I see one nice project

« Last post by Grit Clef on September 24, 2024, 04:22:25 pm »

And in my repository, the svn revision and the wxWidgets version now can be Automatically detected.

Thanks for the info. My github action code for created the release package is mainly created by chatGPT, and has some flaws. I got some warning message like below:

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/create-release@v1, actions/upload-release-asset@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

I think I will use your method, and by adding some time stamp for the release.

Question: why do you add a cron section?

Code

  schedule:
    - cron: '0 0 7,14,21,28 * *'

You want to run the github action every week? (chatGPT gives me the answer: the cron expression '0 0 7,14,21,28 * *' means that the job will run at midnight on the 7th, 14th, 21st, and 28th day of every month.)

Yes. Because then I won't need to run the Actions manually;
And your commands are accepted, thanks.

86

Using Code::Blocks / Re: Update of documentation CB on Windows

« Last post by ThierryD on September 24, 2024, 04:14:06 pm »

Hi,

Just to illustrate and "for fun", an example of CB project with 64 generations of target on W11 64b, with same C source code (32 and 64 bit, Debug / Release, all declination of "free" compilers C/C++ available on Windows)
If you can configure correctly one compiler C/C++ into CB, then you can configure many...

And, to illustrated also, an example of target DLL in CB project with all of these compilers, two test program with call DLL "implicit" or "explicit" also in CB project, and finally test program in Python (not in CB, but maybe possible) here :
    https://github.com/tdechaize/Test_DLL_ALL

Very very open and simply IDE. Enjoy.

TDE.

87

Development / Re: build bot in the github, I see one nice project

« Last post by ollydbg on September 24, 2024, 03:56:25 pm »

When I looked at the link

[MinGW] make check problem Issue #9115 protocolbuffers/protobuf

or

Make commands not working on Windows 10 at setting check up Issue #297 libcheck/check

It looks like the "DLL_EXPORT" is predefined in the auto configure tool?


EDIT:

I will try this patch below in the github action.

Code

diff --git a/src/include/cbplugin.h b/src/include/cbplugin.h
index 10258e5..a3ce67b 100644
--- a/src/include/cbplugin.h
+++ b/src/include/cbplugin.h
@@ -23,11 +23,11 @@
         #ifdef EXPORT_LIB
             #define PLUGIN_EXPORT __declspec (dllexport)
         #else // !EXPORT_LIB
-            #ifdef BUILDING_PLUGIN
+            #if defined(BUILDING_PLUGIN) || defined(DLL_EXPORT)
                 #define PLUGIN_EXPORT __declspec (dllexport)
-            #else // !BUILDING_PLUGIN
+            #else // !BUILDING_PLUGIN && !DLL_EXPORT
                 #define PLUGIN_EXPORT __declspec (dllimport)
-            #endif // BUILDING_PLUGIN
+            #endif // BUILDING_PLUGIN || DLL_EXPORT
         #endif // EXPORT_LIB
     #endif // PLUGIN_EXPORT
 #else

88

Development / Re: build bot in the github, I see one nice project

« Last post by ollydbg on September 24, 2024, 03:46:57 pm »

I want to remove the hack of the dll export hack in building wxsmith plugin.

Code

# Workaround from msys2: error: definition of static data member 'wxsArrayStringEditorDlg::sm_eventTable' of dllimport'd class
# grep -rl "PLUGIN_EXPORT " src/plugins/contrib/wxSmith | xargs -i sed -i "s/PLUGIN_EXPORT //g" {}

So, I remove the hack above.

Now, I see the build error.

It looks like the dll export declaration is not defined.

But when I checked the build log, I see that:

Code

2024-09-24T11:34:32.2601440Z checking for gcc option to produce PIC... -DDLL_EXPORT -DPIC
2024-09-24T11:34:32.4010899Z checking if gcc PIC flag -DDLL_EXPORT -DPIC works... yes
...
...
...
2024-09-24T12:32:02.1013349Z libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../../../src/include -ID:/msys64/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/msys64/mingw64/include/wx-3.2 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXMSW__ -I../../../../../src/include -I../../../../../src/sdk/wxscintilla/include -DCB_AUTOCONF -DPIC -O2 -ffast-math -fPIC -fexceptions -MT wxsfloatproperty.lo -MD -MP -MF .deps/wxsfloatproperty.Tpo -c wxsfloatproperty.cpp  -DDLL_EXPORT -DPIC -o .libs/wxsfloatproperty.o
...
...
build failed!!!

You see, when building every plugin, the "-DDLL_EXPORT -DPIC" is defined.

But my question is: Where is the "DLL_EXPORT" get defined? I search all the C::B code git repo, and I can't find one.

When I check the cbp files, I see there is no "DLL_EXPORT" defined, instead, in the cbp file, another macro named "BUILDING_PLUGIN", this is core point, because in the

include\cbplugin.h, note this file is included in every cpp file when you need to build a plugin.

Code

#ifdef __WXMSW__
    #ifndef PLUGIN_EXPORT
        #ifdef EXPORT_LIB
            #define PLUGIN_EXPORT __declspec (dllexport)
        #else // !EXPORT_LIB
            #ifdef BUILDING_PLUGIN
                #define PLUGIN_EXPORT __declspec (dllexport)
            #else // !BUILDING_PLUGIN
                #define PLUGIN_EXPORT __declspec (dllimport)
            #endif // BUILDING_PLUGIN
        #endif // EXPORT_LIB
    #endif // PLUGIN_EXPORT
#else
    #define PLUGIN_EXPORT
#endif

So, I think we need to solve this issue.

I even checked the configure.ac file or Makefile.am file, I don't find the DLL_EXPORT definition.

Is this value a predefined string?

89

Using Code::Blocks / Re: Workspace Stopped Opening Project File

« Last post by Miguel Gimenez on September 23, 2024, 12:31:39 pm »

Probably the project was corrupted.

90

Help / Re: Codeblocks can't build and run on my macOs.

« Last post by AndrewCot on September 23, 2024, 11:04:00 am »

Use google as there is a page that has the info for fixing the issue you are seeing, BUT debugging will not work. As such you are better trying a different IDE on the MAC that support debugging and has devs that use the MAC.