I installed VS2019, CONNECT and its SDK and I can compile the examples without a problem..
I am trying convert an MDL from SS3 to CONNECT. It is already in .DLL form and compiles within VS in SS3.
When the compiler gets to the type resource, I get this error:
[== Building D:\Users\KWA0GSU\AppData\Local\Temp\Bentley\MicroStationSDK\objects\fplcmd.rsc, (D:\fpl\devStudio\fplmdl\src\fplcmd.r) ==]rcomp @D:\Users\KWA0GSU\AppData\Local\Temp\Bentley\MicroStationSDK\objects\make.optMicroStation Resource Compiler 10.16.01BMAKE: no rules to build D:\Users\KWA0GSU\AppData\Local\Temp\Bentley\MicroStationSDK\objects\fpltyp.rBMAKE: call trace line: 69, D:\fpl\devStudio\fplmdl\src\fplmdl.mkeMon Apr 04 15:30:20 2022, elapsed time: 0:00
My make file looks virtually identical to the myapp.mke example that compiles without error. Does anybody have any idea what could be going wrong here?
#------------------------------------------------------------------------# Generate command table include & resource file using rcomp#------------------------------------------------------------------------$(o)fplcmd.h : $(baseDir)fplcmd.r
$(o)fplcmd.rsc : $(baseDir)fplcmd.r
#------------------------------------------------------------------------# Create & compile the app's type resource using rsctype & rcomp#------------------------------------------------------------------------$(o)fpltyp.r : $(baseDir)$fpltyp.mt \ $(privateInc)fplids.h
$(o)fpltyp.rsc : $(o)fpltyp.r
#------------------------------------------------# Set up to use dlmcomp.mki and dlmlink.mki#------------------------------------------------
Hi Ken Adams,
There are many changes in: product, code and workflows; between MicroStation V8 and MicroStation CONNECT. We try to put as much information possible under the wiki topic Migrating to CONNECT. Where one of the first recommendations would be to Migrate V8 MDL Applications To Native Code (V8i to CONNECT). This helps ensure many coding errors will be caught by the Visual Studio compiler and to ensure the project builds cleanly as a V8 Native Code project. If this step has been performed, then it is best to review what functionality the new product can effectively replace (commands, utilities and workflows) so-as to eliminate any unnecessary coding (or re-inventing the wheel) and not integrating well within the new product/platform.
Once you established the necessary code to be migrated there are two approaches/paths to leverage. Most developers will try to perform a 1:1 migration of source code (line by line); where many times it will be more effective to create a new project, new code and new (modern) APIs to create the most maintainable code most quickly. Given that and your current problem (first encountered) is a problem in the make file, I suggest taking the (very similar) Myapp.mke and Myapp.mki files renaming the app name Myapp to your app name (convention) thereby verifying the source file name (parts) and extensions as being correct and a good starting point for your app to best build cleanly.
Migrating your first couple source code projects will take more time to process in the beginning until (standard) build and compiler errors become second nature to correct, it is worth noting there are a couple workflow related items in the SDK that may help you find information you need (or provide) more conveniently.
HTH,Bob