[DiscordArchive] I assue u have auth challenge, auth session and encrypt mode (both sides). and then auth challenge?
[DiscordArchive] I assue u have auth challenge, auth session and encrypt mode (both sides). and then auth challenge?
Original source
oh that is because someone was lazy and efsw is unconditionally appended to link libraries of game project
rektbyfaith
06-01-2024, 02:03 PM #11Archived author: Tea • Posted: 2024-06-01T14:03:47.515000+00:00
Original source
oh that is because someone was lazy and efsw is unconditionally appended to link libraries of game project
Original source
so the code you see in efsws cmakelists is just a way to not compile it on static tc builds
rektbyfaith
06-01-2024, 02:04 PM #12Archived author: Tea • Posted: 2024-06-01T14:04:13.716000+00:00
Original source
so the code you see in efsws cmakelists is just a way to not compile it on static tc builds
Original source
I see
rektbyfaith
06-01-2024, 02:06 PM #13Archived author: Foe • Posted: 2024-06-01T14:06:21.948000+00:00
Original source
I see
Original source
and no, that if block is not there in efsw upstream repo
rektbyfaith
06-01-2024, 02:06 PM #14Archived author: Tea • Posted: 2024-06-01T14:06:29.924000+00:00
Original source
and no, that if block is not there in efsw upstream repo
Original source
Would it not be ideal to allow building it on static builds as well, and not just when dynamic linking is selected in cmake? Just less of a headache not having to deal with yet another external dependency
rektbyfaith
06-01-2024, 02:14 PM #15Archived author: Foe • Posted: 2024-06-01T14:14:39.737000+00:00
Original source
Would it not be ideal to allow building it on static builds as well, and not just when dynamic linking is selected in cmake? Just less of a headache not having to deal with yet another external dependency
Original source
how about -DWITH_EFSW cmake option (forced with dynamic linking)
rektbyfaith
06-01-2024, 02:20 PM #16Archived author: Tea • Posted: 2024-06-01T14:20:12.506000+00:00
Original source
how about -DWITH_EFSW cmake option (forced with dynamic linking)
Original source
Yeah that would be a decent approach I think, I could just set that when Eluna is enabled then
rektbyfaith
06-01-2024, 02:20 PM #17Archived author: Foe • Posted: 2024-06-01T14:20:54.070000+00:00
Original source
Yeah that would be a decent approach I think, I could just set that when Eluna is enabled then
Original source
```
if(BUILD_SHARED_LIBS OR ELUNA)
set(WITH_EFSW ON)
else()
set(WITH_EFSW OFF)
endif()
```
I'll just do something like this
rektbyfaith
06-01-2024, 02:25 PM #18Archived author: Foe • Posted: 2024-06-01T14:25:59.881000+00:00
Original source
```
if(BUILD_SHARED_LIBS OR ELUNA)
set(WITH_EFSW ON)
else()
set(WITH_EFSW OFF)
endif()
```
I'll just do something like this
Original source
Actually, I'll just default it to off, force enable with shared libs or eluna, and allowing users to override with -DWITH_EFSW
rektbyfaith
06-01-2024, 02:36 PM #19Archived author: Foe • Posted: 2024-06-01T14:36:03.302000+00:00
Original source
Actually, I'll just default it to off, force enable with shared libs or eluna, and allowing users to override with -DWITH_EFSW
Original source
<:angy:1179819827062374410> im genuinely destroyed and more clueless than before, like this doesnt make sense <:wkek:674273318832046131> sending the exactly same packet in node makes the client send char enum packet
rektbyfaith
06-01-2024, 02:38 PM #20Archived author: Widget • Posted: 2024-06-01T14:38:15.726000+00:00
Original source
<:angy:1179819827062374410> im genuinely destroyed and more clueless than before, like this doesnt make sense <:wkek:674273318832046131> sending the exactly same packet in node makes the client send char enum packet
1 Guest(s)
1 Guest(s)