Skip to content

Change destination of ifc-printer binary #46

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

whoan
Copy link

@whoan whoan commented Oct 14, 2023

Changing destination of ifc-printer after conversation in #34 (comment)

Copy link
Contributor

@friendlyanon friendlyanon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The printer itself is ephemeral based on Gabriel's description of what kind of binary tool the SDK will have, so I made it entirely optional. I added this install rule just so you can cleanly get the executable out of the binary directory.

@GabrielDosReis
Copy link
Collaborator

The printer itself is ephemeral based on Gabriel's description of what kind of binary tool the SDK will have

Indeed, the direction we want is to have a general tool (say ifc or ifc.exe executable) that dispatches requests to dedicate binaries (executable or shared libraries/DLLs). For example, the effect of ifc-pinter.exe is to be accomplished with ifc print command.

@whoan whoan force-pushed the change-ifc-printer-destination branch from 5c54e6c to 2b816f4 Compare November 1, 2023 21:37
@whoan
Copy link
Author

whoan commented Nov 1, 2023

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

Successfully merging this pull request may close these issues.

3 participants