Hi Olga,

When packaging software we already use a variety of tools to extract information from executables and libraries. I don't think adding another tool for inspecting a file and dumping out the info required for module compilation is an obviously unreasonable proposal.

                   Peter

From: SG15 <sg15-bounces_at_[hidden]> On Behalf Of Olga Arkhipova via SG15
Sent: 06 February 2022 23:45
To: Jon Chesterfield <jonathanchesterfield_at_[hidden]>; sg15_at_[hidden]
Cc: Olga Arkhipova <olgaark_at_[hidden]>
Subject: Re: [SG15] Meeting on February 4th at 9AM Pacific

EXTERNAL MAIL
>> What's the point of embedding information in a second file next to the first one, when it could be written directly into the first one?

Only the compiler currently can read and write BMI, but anybody can read and write a json file. The ability to write (and not only read) is needed in package production where source/dependencies locations might be different than in the original build.

Olga

From: Jon Chesterfield <jonathanchesterfield_at_[hidden]<mailto:jonathanchesterfield_at_[hidden]>>
Sent: Thursday, February 3, 2022 18:43
To: sg15_at_[hidden]<mailto:sg15_at_[hidden]>
Cc: Olga Arkhipova <olgaark_at_[hidden]<mailto:olgaark_at_[hidden]>>; Steve Downey <sdowney_at_[hidden]<mailto:sdowney_at_[hidden]>>
Subject: Re: [SG15] Meeting on February 4th at 9AM Pacific

You don't often get email from jonathanchesterfield_at_[hidden]<mailto:jonathanchesterfield_at_[hidden]>. Learn why this is important<https://urldefense.com/v3/__http:/aka.ms/LearnAboutSenderIdentification__;!!EHscmS1ygiU1lA!TlEMPliJOIsomIAtS83x4Jli0GvfMsM9925BDt1GM0Q3iA2H9LemHnwgZX3z7g$>
What's the point of embedding information in a second file next to the first one, when it could be written directly into the first one?

Jon

On Fri, 4 Feb 2022, 01:44 Steve Downey via SG15, <sg15_at_[hidden]<mailto:sg15_at_[hidden]>> wrote:


On Thu, Feb 3, 2022 at 8:07 PM Olga Arkhipova <olgaark_at_[hidden]<mailto:olgaark_at_[hidden]>> wrote:
The compiler will have to find all BMIs so their locations should be defined by some command line options.
My point is that the same options can be used to find the .d.json files.

Thanks,
Olga
I agree that if the build system can figure out how to do one, it can do the other, as long as there is some discernible relationship between the bmi and the .d.json file. But in a typical unixy environment, libraries and other artifacts to be consumed are not separated out. Perhaps, though the bmi and .d.json both live together in an isolated filesystem-like thing based on the module name? E.g. a directory or zip file, or some such. On the other hand, since .d.json is intended to be portable, I would expect to find it in something like /usr/share/module_${name} in an FHS style system? Or if a library provides multiple modules, underneath /usr/share/lib${name}/?
Replace /usr with /usr/local/, ~, ${etcetera}, etc above.

(sorry I sent this only to Olga, now replying on list, Olga if you reply, either here or add the list back?)
_______________________________________________
SG15 mailing list
SG15_at_[hidden]<mailto:SG15_at_[hidden]>
https://lists.isocpp.org/mailman/listinfo.cgi/sg15<https://urldefense.com/v3/__https:/nam06.safelinks.protection.outlook.com/?url=https*3A*2F*2Flists.isocpp.org*2Fmailman*2Flistinfo.cgi*2Fsg15&data=04*7C01*7Colgaark*40microsoft.com*7C0871d076a6ec4baff0d208d9e788252e*7C72f988bf86f141af91ab2d7cd011db47*7C1*7C0*7C637795394965328516*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000&sdata=n*2F7OrqnjQqvVqwIMHe8dN6C3ShQE7Z*2BP2oaaxfZeMjs*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUl!!EHscmS1ygiU1lA!TlEMPliJOIsomIAtS83x4Jli0GvfMsM9925BDt1GM0Q3iA2H9LemHnwIbUsIzA$>