Dependencies: Sockpp fails to build on Cygwin. #67

New Issue

BodgeMaster · 2022-10-27T03:51:22+02:00

BodgeMaster commented

2022-10-27 03:51:22 +02:00

When digging into why, I found that sockpp thinks it is being built against Windows libs when building against Cygwin. However, patching that out only reveals more problems as Cygwin itself appears to be missing a bunch of things sockpp expects to be there.

This is not a problem now but it will be for when we actually want to ship something.

There are three ways to handle this:

Ignore it.
While being the easiest, this will ultimately lead to fewer users. Windows users tend to not be the most technical ppl so they will probably not want to deal with WSL or similar where we could just provide a more traditional installer that ships Cygwin as part of the distribution instead. Also ppl don’t want to go through a bunch of manual setup to try out software.
Fix Sockpp.
Unknown amount of work. We might be able to upstream this. Seems like a good option if it’s not too much work.
Build it against Windows.
If it works, relatively little work. Assuming this works, we could just build sockpp against the Windows API and use the resulting DLLs in the project. This will, however, most likely require actual Windows development tools which will make the build process more complex.

When digging into why, I found that sockpp thinks it is being built against Windows libs when building against Cygwin. However, patching that out only reveals more problems as Cygwin itself appears to be missing a bunch of things sockpp expects to be there. This is not a problem now but it will be for when we actually want to ship something. There are three ways to handle this: 1) __Ignore it.__ While being the easiest, this will ultimately lead to fewer users. Windows users tend to not be the most technical ppl so they will probably not want to deal with WSL or similar where we could just provide a more traditional installer that ships Cygwin as part of the distribution instead. Also ppl don’t want to go through a bunch of manual setup to try out software. 2) __Fix Sockpp.__ Unknown amount of work. We might be able to upstream this. Seems like a good option if it’s not too much work. 3) __Build it against Windows.__ If it works, relatively little work. Assuming this works, we could just build sockpp against the Windows API and use the resulting DLLs in the project. This will, however, most likely require actual Windows development tools which will make the build process more complex.

BodgeMaster added the

Workflow

Distribution

Discussion

labels 2022-10-27 03:52:44 +02:00

SodaFountainOfFullLiqourBar commented

2022-10-28 15:55:51 +02:00

I Can Offer a Windows Development box, and when we distribute it we will have to distribute our main exe built. I use evlipse for my dev enviroment. Plugin list needed (eclipse ones)
If possible, we can try and build a compatible compiler into our foss-VG launcher.

I Can Offer a Windows Development box, and when we distribute it we will have to distribute our main exe built. I use evlipse for my dev enviroment. Plugin list needed (eclipse ones) If possible, we can try and build a compatible compiler into our foss-VG launcher.

BodgeMaster commented

2022-10-28 16:33:13 +02:00

Poster

I have a Windows box, that’s not a problem.
(Otherwise, I wouldn’t know this doesn’t work lol)

Edit: Typo

I have a Windows box, that’s not a problem. (Otherwise, I wouldn’t know this doesn’t work lol) Edit: Typo

BodgeMaster commented

2022-11-12 07:34:41 +01:00

Poster

Option 2 was chosen, Sockpp is getting patched on the fly while setting up the project.

Unfortunately, the produced cygdll doesn’t work.

Option 2 was chosen, Sockpp is getting patched on the fly while setting up the project. Unfortunately, the produced cygdll doesn’t work.