Support Board

• Support Board |
• Search Board |
• Control Panel |
• View My Posts / Threads |
• Direct Messages

Date/Time: Tue, 10 Nov 2026 23:50:08 +0000

[Programming Help] - Custom Study Remote Build or custom study enumeration changes lately??

View Count: 43

[Page 1 of 1] First Page -- 1 -- Last Page

[2026-11-10 20:26:18] #1 [Go To First Post]
User275839 - Posts: 76
Hello - I have been using string variants to track changes to custom studies I create. Basically like this: >> at top of file SCDLLName("MyStudy_v01") (_v02, _v03, etc,) >> within setDefaults if (sc.SetDefaults) {     // Set the configuration and defaults          sc.GraphName = "MyStudy_v01"; (_v02, _v03, etc,)          sc.StudyDescription = "MyStudy_v01"; (_v02, _v03, etc,) } >> study entry point (function export) SCSFExport scsf_MyStudy(SCStudyGraphRef sc) (function name never changes) ----------------- This has always worked in the past. I could see all my versions enumerated and listed in the "Add Custom Study" dialog. Now, the remote build process will indeed spit out a DLL file labeled with the _v01, _v02, etc filename, but the the Add Custom Study dialog will not show the different versions. It seems to stop enumeration on the first instance of the SCSFExport exported function name and will not show subsequent instances. Did you change something about the remote build process or the custom study enumeration logic?
0 Thank you

[2026-11-10 21:50:24] #2 [Go To First Post]
User719512 - Posts: 535
This intrigued me enough to see if Sierra changes related to releasing the same DLL for different versions of Sierra might have changed this behavior. A quick repro of what you describe does not repro on my machine. Or my repro does not match your test cases. Are you building all your DLLs or are older ones previously built with older versions of Sierra from that previous point in time (and might use different headers with different versions, aka: #define SC_DLL_VERSION 2969)?
0 Thank you
FooBarBaz.png / V - Attached On 2026-11-10 21:49:14 UTC - Size: 220.07 KB - 5 views

[2026-11-10 22:21:54] #3 [Go To First Post]
User275839 - Posts: 76
Well so that is very interesting... The behavior you are seeing is basically what I want. And it appears that the build process picks up the DLL name from the SCDLLName define at the file start. One possibly informative oddity... When I recompiled older studies they would show the desired labeling in the filename and module name, and in the parenthesis as well. New builds of new .cpp files don't show the _v01, ... in the parens -- just the SCSFExport function name. I have never put multiple exported function declarations within a single module so I'm not sure about your example showing that. However, in your I am puzzled by why the v3 DLL shows a v3 and v4 function, but there is no function named _v3 in the file. See the attached image to see what my Add Study dialog shows for a new file/new compile (top line) and an old study file recompiled yesterday (bottom line). There are 3 items of interest for me here: - the name of the Study DLL - the string within the parens with the v2969 appended) - the name of the function within the DLL where in the .cpp file do each of those items come from? Date Time Of Last Edit: 2026-11-10 22:29:25
0 Thank you
2026-11-10_14-01-51.png / V - Attached On 2026-11-10 22:21:36 UTC - Size: 11.37 KB - 7 views

[2026-11-10 22:38:40] #4 [Go To First Post]
User275839 - Posts: 76
Wa ha ha!! Now the behavior is back to what it was before!! I did a v1 and v2 build (as described in my original post) and they both show up in the Add Study dialog, marked as expected. Maybe it's something in Sierra build system and it depends on what server you are routed to? Or maybe they saw my post and changed something? See the attached PNG to see what I'm seeing now.
0 Thank you
2026-11-10_14-35-49.png / V - Attached On 2026-11-10 22:38:32 UTC - Size: 11.44 KB - 5 views

[Page 1 of 1] First Page -- 1 -- Last Page