search

kaby76 / Antlr4BuildTasks

Third-party build tool for 'Official' Antlr4 tool and runtime parsers using .Net. Drop-in replacement for 'Antlr4cs' Antlr4 tool and build rules.
MIT License
73 stars 10 forks source link

Nuget has contains debug build #62

Open rstm-sf opened 1 year ago

rstm-sf commented 1 year ago

Nuget has contains debug build , see

https://github.com/kaby76/Antlr4BuildTasks/blob/fead9d489106d2956b9c2825427617aea6c08db2/build.sh#L24

kaby76 commented 1 year ago

It is debug so crashes can be traced. Is there an issue?

rstm-sf commented 1 year ago

There are no problems, but I somehow got used to using the release build, because, for example, optimization is turned on there. And I don’t know about stack trace problems with release builds

kaby76 commented 1 year ago

Release builds don't have a stack trace.

The main problem with the package is that it is included downsteam to a build. Once the build is done the package should then be removed in the user's Release or Debug output directory. But I didn't think of this before. This seems not too hard to do in Antlr4BuildTasks.targets.

rstm-sf commented 1 year ago

Release builds don't have a stack trace.

I'm sorry, but this is news to me. F. ex. see https://stackoverflow.com/a/3137915

rstm-sf commented 1 year ago

Once the build is done the package should then be removed in the user's Release or Debug output directory

Can't we use PrivateAssets? https://stackoverflow.com/a/65297502

kaby76 commented 1 year ago

I need to see as much information in a stack trace. Privateassets works but only with "dotnet publish", which I hardly do.