Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Variable output file names #29

Open
basejumpa opened this issue Sep 8, 2022 · 1 comment
Open

Variable output file names #29

basejumpa opened this issue Sep 8, 2022 · 1 comment
Assignees
Milestone

Comments

@basejumpa
Copy link
Member

basejumpa commented Sep 8, 2022

Following requirement shall be satisfied by HamMocKing:

  • Req_HammocKing_0001: There shall be an optional command line argument to define file names of the output files. Templating-Engine shall know about the filename(s). Usecase: gmock/mockup.cc.j2 contains an include-statement which needs to be adapted to the target filename of template gmock/mockup.h.j2.

Additional work shall be done within this issue:

  • Add a new chapter "Design" to documentation (in a new file)
  • Add a new chapter "Requirements" to documentation (in a new file)
  • Start the list of requirements with above one.

We need a new release for it by the end of 2022CW36.4.THU because spldemo needs it via dependendy to spl-core .

@basejumpa basejumpa added this to the 0.3.0 milestone Sep 8, 2022
@basejumpa basejumpa changed the title Variable output filenames Variable output file names Sep 8, 2022
@basejumpa
Copy link
Member Author

Suggested design alternatives:

Alternative_A:

$ hamMocKing --defines "comp=CurrCv" alex would lead to renaming from template mockup_{comp}.h.j2 to output file: mockup_CurrCv.h

Alternative_B:

$ hammocking --suffix _CurrCv .... # Internally the template engine needs variable ${suffix}

We prefer _B. Reason: We postpone _A before we implement the user defined template directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants