I'd like to share some information to use pedeps inside a github action

[asmwarrior]

See my post here in Code::Blocks forum:

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

The final goal is to use this tool to create a standalone C::B packages inside the github action. Thanks.

[brechtsanders]

I was planning to meet the maker of Code::Blocks (who lives about a 1 hour drive from me) to discuss how winlibs and Code::Blocks can come together, but our plans changed and we haven't rescheduled yet.

I have built my own build system and package manager, but have not yet properly documented and tested it, and I haven't figured out if all licenses allow me to distribute binaries and where I would host these.

Can you describe exactly what I could do to support your ideas?

Or if you like we could set op a call.

[asmwarrior]

I was planning to meet the maker of Code::Blocks (who lives about a 1 hour drive from me) to discuss how winlibs and Code::Blocks can come together, but our plans changed and we haven't rescheduled yet.

That's nice idea. I really appreciate about the compiler suite and other tools you made.

I have built my own build system and package manager, but have not yet properly documented and tested it, and I haven't figured out if all licenses allow me to distribute binaries and where I would host these.

Currently, I use msys2/mingw64 gcc and other packages, they are very easy to install. One issue is that they are dropping the windows 7 OS support sooner or later, but some of my clients are still using windows 7.

If you are using a new build system, that's be great!

Can you describe exactly what I could do to support your ideas?

Or if you like we could set op a call.

I'm one of Code::Blocks developer, and what I want to do is to use pedeps tool to copy all the dependency dlls when I build a Code::Blocks from github actions. It is nearlly done, see this post: Re: build bot in the github, I see one nice project

I think many other project hosted in github can use your pedeps tool to ship their dependency dlls, and this make creating a release package very easily.

And currently, I think a call is not necessary, my English is not good enough. Thanks.

[asmwarrior]

FYI:

In my project: asmwarrior/x86-codeblocks-builds: Automatically built codeblocks for both 32b and 64b Windows systems.

I can now create a full C::B win64 bit release package(include all the exe and dll) from github action. The copying of the dlls are mainly done by pedeps.

[brechtsanders]

That's great news.

copypedeps should copy all files that it finds in the PATH environment variable that are not in the Windows folder.

So your script may need to add locations to the PATH environment variable if everything is not in the same folder.

[asmwarrior]

That's great news.

copypedeps should copy all files that it finds in the PATH environment variable that are not in the Windows folder.

So your script may need to add locations to the PATH environment variable if everything is not in the same folder.

In the github action, I run your copypedepes.exe inside a msys2 ming64 shell, and I see the bin folder of the gcc is already added in the PATH, so dll files get copied correctly.

I see the result C::B works OK.