Use AWSLC_SOURCE_DIR and AWSLC_BINARY_DIR

[justsmth]

Description of changes:

• Use slightly less ambiguous AWSLC_SOURCE_DIR and AWSLC_BINARY_DIR instead of PROJECT_SOURCE_DIR and PROJECT_BINARY_DIR.

Call-outs:

• No change to logic. The change is a simple text substitution.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.06%. Comparing base (ead47e8) to head (9f10262).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2208      +/-   ##
==========================================
+ Coverage   79.04%   79.06%   +0.02%     
==========================================
  Files         612      612              
  Lines      106222   106222              
  Branches    15008    15007       -1     
==========================================
+ Hits        83959    83984      +25     
+ Misses      21612    21587      -25     
  Partials      651      651              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[andrewhop]

Was this causing an issue? Is it worth putting some pre-push check that ensures there are no PROJECT variables in our CMakeList?

[justsmth]

Was this causing an issue? Is it worth putting some pre-push check that ensures there are no PROJECT variables in our CMakeList?

I don't think it was causing any actual problems for us. I noticed it while debugging a build issue and I got concerned about which "project" was in context. The use of PROJECT_SOURCE_DIR is a potential source of ambiguity when working with third-party libraries (like jitterentropy).