Create Linux AppImage #644

Closed
opened 2026-01-29 16:49:59 +00:00 by claunia · 19 comments
Owner

Originally created by @cfsmp3 on GitHub (Jun 13, 2021).

The old build static script is useless. Let's replace it with AppImage as suggested ina comment below

Originally created by @cfsmp3 on GitHub (Jun 13, 2021). The old build static script is useless. Let's replace it with AppImage as suggested ina comment below
Author
Owner

@canihavesomecoffee commented on GitHub (Jun 13, 2021):

It clones from master, so it will build the most recent... However the deps might not be up to date at all.

@canihavesomecoffee commented on GitHub (Jun 13, 2021): It clones from master, so it will build the most recent... However the deps might not be up to date at all.
Author
Owner

@cfsmp3 commented on GitHub (Jun 13, 2021):

It clones from master, so it will build the most recent... However the deps might not be up to date at all.

Ah yes. We just like to leave irrelevant comments around

# wget https://sourceforge.net/projects/ccextractor/files/ccextractor/0.82/ccextractor.src.0.82.zip;
@cfsmp3 commented on GitHub (Jun 13, 2021): > It clones from master, so it will build the most recent... However the deps might not be up to date at all. Ah yes. We just like to leave irrelevant comments around ``` # wget https://sourceforge.net/projects/ccextractor/files/ccextractor/0.82/ccextractor.src.0.82.zip; ```
Author
Owner

@cfsmp3 commented on GitHub (Mar 22, 2023):

@prateekmedia could you check this out? Probably you can fix it without a lot of pain.

Better - just make -static an arg to build :-)

@cfsmp3 commented on GitHub (Mar 22, 2023): @prateekmedia could you check this out? Probably you can fix it without a lot of pain. Better - just make -static an arg to build :-)
Author
Owner

@prateekmedia commented on GitHub (Mar 22, 2023):

Will look at it

@prateekmedia commented on GitHub (Mar 22, 2023): Will look at it
Author
Owner

@prateekmedia commented on GitHub (Mar 22, 2023):

@cfsmp3 Could you explain what needs to be done in this? I looked at the file, ran it and it gave ccextractor-README.txt not found error.

@prateekmedia commented on GitHub (Mar 22, 2023): @cfsmp3 Could you explain what needs to be done in this? I looked at the file, ran it and it gave `ccextractor-README.txt` not found error.
Author
Owner

@cfsmp3 commented on GitHub (Mar 22, 2023):

@cfsmp3 Could you explain what needs to be done in this? I looked at the file, ran it and it gave ccextractor-README.txt not found error.

This will give you some context

https://github.com/CCExtractor/ccextractor/issues/597

Note that I renamed the script from @traceypooh to build-static.sh without actually changing the context (not a great idea, I realize).

Still, the script is obsolete now but the idea is good.

Are we able to produce a static binary using Docker as container? (docker is great for this because you can have a reliable environment no matter the starting point in the host).

If you think that's not possible, or really a lot of work, I guess we should just remove build-static.sh for now because obviously it's not working and it's just going to confuse people.

@cfsmp3 commented on GitHub (Mar 22, 2023): > @cfsmp3 Could you explain what needs to be done in this? I looked at the file, ran it and it gave `ccextractor-README.txt` not found error. This will give you some context https://github.com/CCExtractor/ccextractor/issues/597 Note that I renamed the script from @traceypooh to build-static.sh without actually changing the context (not a great idea, I realize). Still, the script is obsolete now but the idea is good. Are we able to produce a static binary using Docker as container? (docker is great for this because you can have a reliable environment no matter the starting point in the host). If you think that's not possible, or really a lot of work, I guess we should just remove build-static.sh for now because obviously it's not working and it's just going to confuse people.
Author
Owner

@prateekmedia commented on GitHub (Mar 22, 2023):

I will try to do some testing from my side, let's see if I get it working.

@prateekmedia commented on GitHub (Mar 22, 2023): I will try to do some testing from my side, let's see if I get it working.
Author
Owner

@prateekmedia commented on GitHub (Mar 23, 2023):

@cfsmp3 I think building static is not something we should do, instead why not build an AppImage (which is a universal format) and it will be able to run without being dependent on the system dependencies.

@prateekmedia commented on GitHub (Mar 23, 2023): @cfsmp3 I think building static is not something we should do, instead why not build an AppImage (which is a universal format) and it will be able to run without being dependent on the system dependencies.
Author
Owner

@cfsmp3 commented on GitHub (Mar 23, 2023):

@cfsmp3 I think building static is not something we should do, instead why not build an AppImage (which is a universal format) and it will be able to run without being dependent on the system dependencies.

That's a really good idea.
It would also solve the eternal issues with tesseract training files, etc

@cfsmp3 commented on GitHub (Mar 23, 2023): > @cfsmp3 I think building static is not something we should do, instead why not build an AppImage (which is a universal format) and it will be able to run without being dependent on the system dependencies. That's a really good idea. It would also solve the eternal issues with tesseract training files, etc
Author
Owner

@prateekmedia commented on GitHub (Mar 23, 2023):

@cfsmp3 Do you mean that tessdata should not be in the AppImage itself but installed separately?

@prateekmedia commented on GitHub (Mar 23, 2023): @cfsmp3 Do you mean that tessdata should not be in the AppImage itself but installed separately?
Author
Owner

@cfsmp3 commented on GitHub (Mar 23, 2023):

@cfsmp3 Do you mean that tessdata should not be in the AppImage itself but installed separately?

No, the opposite! If we could have a AppImage that included tessdata it would be fantastic.

And if the image came from the CI so we could always have a known good nightly it would solve most of our issues with fixes taking forever to reach users because we release a new version once a year or so.

@cfsmp3 commented on GitHub (Mar 23, 2023): > @cfsmp3 Do you mean that tessdata should not be in the AppImage itself but installed separately? No, the opposite! If we could have a AppImage that included tessdata it would be fantastic. And if the image came from the CI so we could always have a known good nightly it would solve most of our issues with fixes taking forever to reach users because we release a new version once a year or so.
Author
Owner

@prateekmedia commented on GitHub (Mar 23, 2023):

yes

@prateekmedia commented on GitHub (Mar 23, 2023): yes
Author
Owner

@IshanGrover2004 commented on GitHub (Jan 23, 2024):

Hey, Can i try making AppImage in replace of build-static.sh file
Or this issue is just for the CCExtracter team?

@IshanGrover2004 commented on GitHub (Jan 23, 2024): Hey, Can i try making AppImage in replace of build-static.sh file Or this issue is just for the CCExtracter team?
Author
Owner

@cfsmp3 commented on GitHub (Jan 23, 2024):

You can work on it

@cfsmp3 commented on GitHub (Jan 23, 2024): You can work on it
Author
Owner

@IshanGrover2004 commented on GitHub (Jan 23, 2024):

You can work on it

Okk then
I'll research and will open PR after working on it

Any information I should know before working on it?

@IshanGrover2004 commented on GitHub (Jan 23, 2024): > You can work on it Okk then I'll research and will open PR after working on it Any information I should know before working on it?
Author
Owner

@prateekmedia commented on GitHub (Jan 23, 2024):

@IshanGrover2004 You can began by reading appimage creation documentation and look at how other softwares are packaging the appimage.

@prateekmedia commented on GitHub (Jan 23, 2024): @IshanGrover2004 You can began by reading appimage creation documentation and look at how other softwares are packaging the appimage.
Author
Owner

@IshanGrover2004 commented on GitHub (Jan 23, 2024):

Yes, already started reading official AppImage docs

@IshanGrover2004 commented on GitHub (Jan 23, 2024): Yes, already started reading official AppImage docs
Author
Owner

@IshanGrover2004 commented on GitHub (Jan 25, 2024):

Hi,
I have studied about AppImage from its official docs and have gained a good understanding of how it is created and red the build-static.sh file.
The build-static.sh file contains so many not working commands and links.
I am planning to make a .sh file which will run a docker alpine and setup the static library binary through which ccextracter binary file will be made which will be further placed it into AppDir and make final .AppImage file and then cleanup everything. I want to confirm if my approach is correct.

@IshanGrover2004 commented on GitHub (Jan 25, 2024): Hi, I have studied about AppImage from its official docs and have gained a good understanding of how it is created and red the `build-static.sh` file. The `build-static.sh` file contains so many not working commands and links. I am planning to make a `.sh` file which will run a docker alpine and setup the static library binary through which `ccextracter` binary file will be made which will be further placed it into `AppDir` and make final `.AppImage` file and then cleanup everything. I want to confirm if my approach is correct.
Author
Owner

@IshanGrover2004 commented on GitHub (Jan 30, 2024):

I have opened PR #1592 . Can anyone from CCExtractor team look on it, so that i resolve current issues in there.

@IshanGrover2004 commented on GitHub (Jan 30, 2024): I have opened PR #1592 . Can anyone from CCExtractor team look on it, so that i resolve current issues in there.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ccextractor#644