Getting started with the regular archives

Since 2020.4 ODA SDK can be compiled using C++17 standard.

We had dropped support for gcc4.8 (20.12 release is the last one). Gcc 4.9 is the oldest compiler bundle now.

You can use ftp.opendesign.com.

Username and password are the same as for logging in to the main member download page. Your default directory will be a private home directory that can be used for uploads. Upload your file(s) here.

Place a link to the newly uploaded file in your JIRA report using the following format:

https://www.eu.opendesign.com/clients/<your username>/<uploaded file name>

Example:

https://www.eu.opendesign.com/clients/myname@mycompany.com/VpError.dwg

Note that this link will not be accessible to you via HTTP, but it will be accessible to our development staff, saving us time when processing the issue.

Clients settings:

Filezilla:

WinSCP:

Core FTP LE:

FarManager:

Since 21.2.

You need to install MFC. It doesn't come with default install configuration. Run Visual Studio installer, click "Modify", and select Visual C++ MFC.

You need to install MFC. It doesn't come with default install configuration. Run Visual Studio installer, click "Modify", and select Visual C++ MFC.

Tx is just different file extension, such modules are used only for dynamic loading (similar to .arx in AutoCAD).

You can download past releases on this page.

Please follow this link to resolve this issue.

Once you have logged in at www.opendesign.com , you should have access to Jira.

Jira login is only for ODA Developers - for internal projects. All communications with customers are made via public projects.

This issue may be caused by some of your software (email client etc.). It opened the one-time link before You did this. Since the link can't be used twice You was unable to reset your access. Please email us on support@opendesign.com if you faced this issue.

1. Choose ODA Product and find dependencies on the scheme. Download necessary archives, for example:

• For Civil SDK download Kernel, Drawings, Architecture and Civil;
• For Drawings.NET SDK download Kernel, Drawings, and Drawings.NET;
• For Architecture.NET SDK download Kernel, Drawings, Drawings.NET, Architecture, and Architecture.NET.

Please do not mix archives with different configurations:

• dll - indicates dynamic link library version
• md, mt - /MD, /MT, etc. Visual Studio compiler options (static library)
• dbg - indicates the presence of debug information (/mtd, /mdd, etc.)

2. Unpack downloaded archives and merge them in one folder.

3. Get ODA Activation Information.

4. After login, check your activation name, and if it is correct, choose a version of the ODA platform you use and click the Generate.

You can see it in the archives name. Please, note that vc (Visual C++) version doesn’t always exactly have the same number as Visual Studio version:

vc = Visual Studio version

8==2005,

9==2008,

10==2010,

11==2012,

12==2013,

14==2015,

15==2017.

16==2019

These archives have different configurations:

• dll - indicates dynamic link library version;
• md, mt - Visual Studio compiler options (static library);
• dbg - indicates the presence of debug information (/mtd, /mdd, etc.);
• rwd - release build containing debug information (useful for reproducing certain types of runtime problems);
• amd64 - libraries built for the x86 AMD64 platform.

More information about naming conventions for archivescan be found here.

You shouldn’t mix archives with different configurations (even mixing dll and dlldbg can cause exceptions).

Use attr->tag ().c_str() and attr->textString ().c_str().
Also this article will be helpful.

This message indicates that the file was created with a non-Autodesk(c) software. As we are independent from Autodesk(c) this message must appear (with both regular and trial archives) as otherwise it will be a violation of the legal terms.

Open the Project Properties in Eclipse and switch to Java Build Path -> Libraries. Add the .jars to the project and specify the "Native library location" setting. Point to the exe/vc10 folder with all of the .exe and .dll files activated.

The TDFILEPRODUCT command prints to the console either an ODA version string or "Unknown": TOOLKIT_EXPORT OdString odFileWasSavedBySoftware(const OdDbDatabase* pDb); This function is not declared in Include headers.

For DLLs and .tx modules you link with, it is the same as for any other DLLs. Their folders should be in the PATH variable.

For .tx modules that are not linked (loaded dynamically with loadModule()), you can override OdRxSystemServices::findModule() and return the full path.

Naming Conventions for Archives

Pleas follow this link:

Migrating to a New ODA Platform Version

ODA login required