|
From: | Jean-Claude Beaudoin |
Subject: | Re: [Tinycc-devel] Tidying TCC's external API |
Date: | Mon, 26 Sep 2016 03:22:12 -0400 |
> I gather that this is for the case where ONE_SOURCE is "not" set, and under a "configure --disable-static" such that tcc is linked againsta libtcc.dll. Am I right?
Right!
I've no precise idea why tcc.c requires pstrcpy:
$ grep strcpy tcc.c
pstrcpy(child_path, sizeof child_path - 40, argv[0]);
strcpy(child_name, target);
pstrcpy(buf, sizeof(buf), target);
pstrcpy(ext, sizeof(buf) - (ext-buf), ".d");
pstrcpy(buf, sizeof(buf), name);
strcpy(ext, ".dll");
strcpy(ext, ".exe");
strcpy(ext, ".o");
strcpy(buf, "a.out");
I see it uses both pstrcpy and strcpy.
[Prev in Thread] | Current Thread | [Next in Thread] |