GitHub build workflows

[Blixibon]

GitHub workflows which automatically build the codebase on VC++ (Windows) and GCC/G++ (Linux).

The workflows will build for the game DLLs, the shaders, and the mapping tools depending on what files the PR modifies. A manual workflow can be used to compile everything in the SDK.

Based on a script created by z33ky. (#162)

This PR should be squashed.

[Blixibon]

@z33ky Out of curiosity, what do you think of the way I implemented this? I used the script you created as a base and diversified it to encompass other parts of the SDK, but I don't know if I did it in the most efficient way.

I also implemented a job for building Linux binaries, but I'm not experienced with Linux development and I'm curious if there's anything about the way I did it which could be more efficient or should be addressed. I have not yet tested the generated binaries in-game.

[1upD]

This looks good to me

[z33ky]

Hi. Very cool.
Sorry for taking some time to reply.

The generated Linux binaries run fine.

You could consider also publishing the debug-info files for release builds as they are stripped off the binaries. On Linux they are also put in the bin/ directory with .dbg suffix (i.e. client.so.dbg). I remember on Windows they were .pdb files.
On Linux at least the debug-builds do not strip the debug-info from the libraries, so publishing the .dbg files there is unnecessary.

[z33ky]

I'm not sure this is necessary, considering the variable is set explicitly in the make call below.

[z33ky]

Is sudo required?

[z33ky]

Note you can use a different separator for sed, like sed -i 's|/hl2 /episodic|/${{inputs.game}}|' which is more easily readable by skipping the need to escape the slashes.

[Blixibon]

GitHub workflows which automatically build the codebase on VC++ (Windows) and GCC/G++ (Linux).

The workflows will build for the game DLLs, the shaders, and the mapping tools depending on what files the PR modifies. A manual workflow can be used to compile everything in the SDK.

Based on a script created by z33ky. (#162)

This PR should be squashed.

[Blixibon]

@z33ky Out of curiosity, what do you think of the way I implemented this? I used the script you created as a base and diversified it to encompass other parts of the SDK, but I don't know if I did it in the most efficient way.

I also implemented a job for building Linux binaries, but I'm not experienced with Linux development and I'm curious if there's anything about the way I did it which could be more efficient or should be addressed. I have not yet tested the generated binaries in-game.

[1upD]

This looks good to me

[z33ky]

Hi. Very cool.
Sorry for taking some time to reply.

The generated Linux binaries run fine.

You could consider also publishing the debug-info files for release builds as they are stripped off the binaries. On Linux they are also put in the bin/ directory with .dbg suffix (i.e. client.so.dbg). I remember on Windows they were .pdb files.
On Linux at least the debug-builds do not strip the debug-info from the libraries, so publishing the .dbg files there is unnecessary.

[z33ky]

I'm not sure this is necessary, considering the variable is set explicitly in the make call below.

[z33ky]

Is sudo required?

[z33ky]

Note you can use a different separator for sed, like sed -i 's|/hl2 /episodic|/${{inputs.game}}|' which is more easily readable by skipping the need to escape the slashes.

[Blixibon]

GitHub workflows which automatically build the codebase on VC++ (Windows) and GCC/G++ (Linux).

The workflows will build for the game DLLs, the shaders, and the mapping tools depending on what files the PR modifies. A manual workflow can be used to compile everything in the SDK.

Based on a script created by z33ky. (#162)

This PR should be squashed.

[Blixibon]

@z33ky Out of curiosity, what do you think of the way I implemented this? I used the script you created as a base and diversified it to encompass other parts of the SDK, but I don't know if I did it in the most efficient way.

I also implemented a job for building Linux binaries, but I'm not experienced with Linux development and I'm curious if there's anything about the way I did it which could be more efficient or should be addressed. I have not yet tested the generated binaries in-game.

[1upD]

This looks good to me

[z33ky]

Hi. Very cool.
Sorry for taking some time to reply.

The generated Linux binaries run fine.

You could consider also publishing the debug-info files for release builds as they are stripped off the binaries. On Linux they are also put in the bin/ directory with .dbg suffix (i.e. client.so.dbg). I remember on Windows they were .pdb files.
On Linux at least the debug-builds do not strip the debug-info from the libraries, so publishing the .dbg files there is unnecessary.

[z33ky]

I'm not sure this is necessary, considering the variable is set explicitly in the make call below.

[z33ky]

Is sudo required?

[z33ky]

Note you can use a different separator for sed, like sed -i 's|/hl2 /episodic|/${{inputs.game}}|' which is more easily readable by skipping the need to escape the slashes.

[Blixibon]

GitHub workflows which automatically build the codebase on VC++ (Windows) and GCC/G++ (Linux).

The workflows will build for the game DLLs, the shaders, and the mapping tools depending on what files the PR modifies. A manual workflow can be used to compile everything in the SDK.

Based on a script created by z33ky. (#162)

This PR should be squashed.

[Blixibon]

@z33ky Out of curiosity, what do you think of the way I implemented this? I used the script you created as a base and diversified it to encompass other parts of the SDK, but I don't know if I did it in the most efficient way.

I also implemented a job for building Linux binaries, but I'm not experienced with Linux development and I'm curious if there's anything about the way I did it which could be more efficient or should be addressed. I have not yet tested the generated binaries in-game.

[1upD]

This looks good to me

[z33ky]

Hi. Very cool.
Sorry for taking some time to reply.

The generated Linux binaries run fine.

You could consider also publishing the debug-info files for release builds as they are stripped off the binaries. On Linux they are also put in the bin/ directory with .dbg suffix (i.e. client.so.dbg). I remember on Windows they were .pdb files.
On Linux at least the debug-builds do not strip the debug-info from the libraries, so publishing the .dbg files there is unnecessary.

[z33ky]

I'm not sure this is necessary, considering the variable is set explicitly in the make call below.

[z33ky]

Is sudo required?

[z33ky]

Note you can use a different separator for sed, like sed -i 's|/hl2 /episodic|/${{inputs.game}}|' which is more easily readable by skipping the need to escape the slashes.

[Blixibon]

GitHub workflows which automatically build the codebase on VC++ (Windows) and GCC/G++ (Linux).

The workflows will build for the game DLLs, the shaders, and the mapping tools depending on what files the PR modifies. A manual workflow can be used to compile everything in the SDK.

Based on a script created by z33ky. (#162)

This PR should be squashed.

[Blixibon]

@z33ky Out of curiosity, what do you think of the way I implemented this? I used the script you created as a base and diversified it to encompass other parts of the SDK, but I don't know if I did it in the most efficient way.

I also implemented a job for building Linux binaries, but I'm not experienced with Linux development and I'm curious if there's anything about the way I did it which could be more efficient or should be addressed. I have not yet tested the generated binaries in-game.

[1upD]

This looks good to me

[z33ky]

Hi. Very cool.
Sorry for taking some time to reply.

The generated Linux binaries run fine.

You could consider also publishing the debug-info files for release builds as they are stripped off the binaries. On Linux they are also put in the bin/ directory with .dbg suffix (i.e. client.so.dbg). I remember on Windows they were .pdb files.
On Linux at least the debug-builds do not strip the debug-info from the libraries, so publishing the .dbg files there is unnecessary.

[z33ky]

I'm not sure this is necessary, considering the variable is set explicitly in the make call below.

[z33ky]

Is sudo required?

[z33ky]

Note you can use a different separator for sed, like sed -i 's|/hl2 /episodic|/${{inputs.game}}|' which is more easily readable by skipping the need to escape the slashes.

[Blixibon]

GitHub workflows which automatically build the codebase on VC++ (Windows) and GCC/G++ (Linux).

The workflows will build for the game DLLs, the shaders, and the mapping tools depending on what files the PR modifies. A manual workflow can be used to compile everything in the SDK.

Based on a script created by z33ky. (#162)

This PR should be squashed.

[Blixibon]

@z33ky Out of curiosity, what do you think of the way I implemented this? I used the script you created as a base and diversified it to encompass other parts of the SDK, but I don't know if I did it in the most efficient way.

I also implemented a job for building Linux binaries, but I'm not experienced with Linux development and I'm curious if there's anything about the way I did it which could be more efficient or should be addressed. I have not yet tested the generated binaries in-game.

[1upD]

This looks good to me

[z33ky]

Hi. Very cool.
Sorry for taking some time to reply.

The generated Linux binaries run fine.

You could consider also publishing the debug-info files for release builds as they are stripped off the binaries. On Linux they are also put in the bin/ directory with .dbg suffix (i.e. client.so.dbg). I remember on Windows they were .pdb files.
On Linux at least the debug-builds do not strip the debug-info from the libraries, so publishing the .dbg files there is unnecessary.

[z33ky]

I'm not sure this is necessary, considering the variable is set explicitly in the make call below.

[z33ky]

Is sudo required?

[z33ky]

Note you can use a different separator for sed, like sed -i 's|/hl2 /episodic|/${{inputs.game}}|' which is more easily readable by skipping the need to escape the slashes.

[Blixibon]

GitHub workflows which automatically build the codebase on VC++ (Windows) and GCC/G++ (Linux).

The workflows will build for the game DLLs, the shaders, and the mapping tools depending on what files the PR modifies. A manual workflow can be used to compile everything in the SDK.

Based on a script created by z33ky. (#162)

This PR should be squashed.

[Blixibon]

@z33ky Out of curiosity, what do you think of the way I implemented this? I used the script you created as a base and diversified it to encompass other parts of the SDK, but I don't know if I did it in the most efficient way.

I also implemented a job for building Linux binaries, but I'm not experienced with Linux development and I'm curious if there's anything about the way I did it which could be more efficient or should be addressed. I have not yet tested the generated binaries in-game.

[1upD]

This looks good to me

[z33ky]

Hi. Very cool.
Sorry for taking some time to reply.

The generated Linux binaries run fine.

You could consider also publishing the debug-info files for release builds as they are stripped off the binaries. On Linux they are also put in the bin/ directory with .dbg suffix (i.e. client.so.dbg). I remember on Windows they were .pdb files.
On Linux at least the debug-builds do not strip the debug-info from the libraries, so publishing the .dbg files there is unnecessary.

[z33ky]

I'm not sure this is necessary, considering the variable is set explicitly in the make call below.

[z33ky]

Is sudo required?

[z33ky]

Note you can use a different separator for sed, like sed -i 's|/hl2 /episodic|/${{inputs.game}}|' which is more easily readable by skipping the need to escape the slashes.

[Blixibon]

GitHub workflows which automatically build the codebase on VC++ (Windows) and GCC/G++ (Linux).

The workflows will build for the game DLLs, the shaders, and the mapping tools depending on what files the PR modifies. A manual workflow can be used to compile everything in the SDK.

Based on a script created by z33ky. (#162)

This PR should be squashed.

[Blixibon]

@z33ky Out of curiosity, what do you think of the way I implemented this? I used the script you created as a base and diversified it to encompass other parts of the SDK, but I don't know if I did it in the most efficient way.

I also implemented a job for building Linux binaries, but I'm not experienced with Linux development and I'm curious if there's anything about the way I did it which could be more efficient or should be addressed. I have not yet tested the generated binaries in-game.

[1upD]

This looks good to me

[z33ky]

Hi. Very cool.
Sorry for taking some time to reply.

The generated Linux binaries run fine.

You could consider also publishing the debug-info files for release builds as they are stripped off the binaries. On Linux they are also put in the bin/ directory with .dbg suffix (i.e. client.so.dbg). I remember on Windows they were .pdb files.
On Linux at least the debug-builds do not strip the debug-info from the libraries, so publishing the .dbg files there is unnecessary.

[z33ky]

I'm not sure this is necessary, considering the variable is set explicitly in the make call below.

[z33ky]

Is sudo required?

[z33ky]

Note you can use a different separator for sed, like sed -i 's|/hl2 /episodic|/${{inputs.game}}|' which is more easily readable by skipping the need to escape the slashes.