Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added automatic build and upload of artifacts #177

Closed
wants to merge 4 commits into from

Conversation

fragolinux
Copy link

it will automatically create a release when a new tag is pushed

@fragolinux
Copy link
Author

probably you'd like to rename "windows" in "cygwin", as it's that, really (i just extended your own github action with the release part)

@bagder
Copy link
Member

bagder commented Apr 27, 2023

I presume these Windows build binaries only work if you have cygwin installed? Then I agree they should be named cygwin.

@fragolinux
Copy link
Author

I presume these Windows build binaries only work if you have cygwin installed? Then I agree they should be named cygwin.

They're just the same builds already in original automation, just added the release and publish part...

on:
push:
tags:
- "v*"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this supposed to match the tags for which to make releases? They are named trurl-* now...

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This automation is triggered only when you push a git tag, in my case I pushed v0.6.0, it's a standard way in gh actions, but you can modify as you want... It makes sense to me, as this way the binaries are created just on a new release, not always

@bagder
Copy link
Member

bagder commented Apr 27, 2023

We should probably also call them "ubuntu" rather than just "linux".

@fragolinux
Copy link
Author

Rename them yourself? Or do you want me to do? Just swap windows for cygwin

@bagder
Copy link
Member

bagder commented Apr 27, 2023

I presume these Windows build binaries only work if you have cygwin installed? Then I agree they should be named cygwin.

They're just the same builds already in original automation, just added the release and publish part...

I don't think that answers my question though?

@fragolinux
Copy link
Author

Lol, I'm just using what you yourself had made, I just renamed (wrongly) cygwin to windows, before realising that without the dll they don't work, of course

@fragolinux
Copy link
Author

We should probably also call them "ubuntu" rather than just "linux".

I didn't even take a look on HOW did you build them: if it's a static build, with no dependencies, this should work everywhere on any linux, I'm not able of help you on this...

@bagder
Copy link
Member

bagder commented Apr 27, 2023

I'm not able of help you on this...

But I talked about if not a rename would make sense. I did not ask you to change the build.

@fragolinux
Copy link
Author

I'm not able of help you on this...

But I talked about if not a rename would make sense. I did not ask you to change the build.

It makes sense if these are, really, just ubuntu builds... If the biraries work on other distros, it's good to have them called linux, otherwise better rename them to ubuntu (really, a specific one, too...)

For the windows ones, better rename windows to cygwin

But I see a new pr of someone who probably made native windows builds, too

@fragolinux fragolinux marked this pull request as draft April 27, 2023 07:34
@fragolinux fragolinux marked this pull request as ready for review April 27, 2023 07:42
@fragolinux
Copy link
Author

i renamed both linux-->ubuntu and windows-->cygwin

@bagder
Copy link
Member

bagder commented Aug 7, 2023

I think the biggest need for this is for native Windows builds, and I also did not manage to get this to work in a local test repo of mine. I think we can put this on hold for now.

@bagder bagder closed this Aug 7, 2023
@fragolinux
Copy link
Author

fragolinux commented Aug 8, 2023

as windows was never a priority for me, and its buids were in your own code (if working or not, you know...), why not just incorporate the PR parts relative to the *nix builds, and strip out the win part? and my builds were perfectly fine as you can see here, just the win part failed, as expected (i don't know how to fix them nor interested into)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants