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.

Sign up for GitHub

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

Jump to bottom

Makefile generation bug for external types #172

Open

nikswamy opened this issue Feb 27, 2025 · 0 comments

Contributor

nikswamy commented Feb 27, 2025 •

edited

Loading

Consider this file: Test.3d

extern typedef struct _A A

entrypoint
typedef struct _B {
    UINT32 b;
} B;

Running this:

.\everparse\everparse.cmd --odir tmp --makefile nmake --makefile_name test.makefile Test.3d --skip_o_rules

A couple of issues:

This produces test.makefile in the current directory rather than in tmp. Is that desirable?
The more significant issue is that the generated Makefile has a cyclic dependence:

$(EVERPARSE_OUTPUT_DIR)\Test.ExternalAPI.fsti.checked : $(EVERPARSE_OUTPUT_DIR)\Test.ExternalAPI.fsti $(EVERPARSE_OUTPUT_DIR)\Test.ExternalTypes.fsti.checked
	$(EVERPARSE_CMD) --odir $(EVERPARSE_OUTPUT_DIR) --__micro_step verify $(EVERPARSE_OUTPUT_DIR)\Test.ExternalAPI.fsti

Without the --skip_o_rules, the command above prints a message "Test has no output types". This should probably not be printed.

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment