I can't build the current head for release (x86) unless I comment out all the EHR code, which is in contained in an #if DEBUG.
The problem code follows the '#else'
How do I fix this?
Building for release, but EHR code generating errors
Building for release, but EHR code generating errors
Cheers,
Bill Starck, DDS
Big Idea Software, LLC
Developer, EASy(Electronic Anesthesia System) for Open Dental
817-807-1709
TX, USA
Bill Starck, DDS
Big Idea Software, LLC
Developer, EASy(Electronic Anesthesia System) for Open Dental
817-807-1709
TX, USA
- jordansparks
- Site Admin
- Posts: 5765
- Joined: Sun Jun 17, 2007 3:59 pm
- Location: Salem, Oregon
- Contact:
Re: Building for release, but EHR code generating errors
Fix committed. Can you tell we don't compile the head in release mode very often?
Jordan Sparks, DMD
http://www.opendental.com
http://www.opendental.com
Re: Building for release, but EHR code generating errors
The issue you're facing seems to be related to conditional compilation directives, specifically the block. When building for release, the code following #else is included, and this section likely contains functionality or references that cause errors in a non-debug context.
To fix this, start by reviewing the code in the block and ensure it is suitable for a release build. It might depend on variables, methods, or libraries that are not properly configured for the release configuration. Addressing any missing dependencies or incomplete implementations in this block should resolve the issue.
If the EHR code is exclusively for debugging purposes, consider refactoring it or ensuring that it doesn’t run in a release build. You can also implement fallback or alternative logic for the release build if needed. After making these changes, test both the debug and release builds to verify that everything works as intended.
For healthcare projects like this, structuring the code efficiently is crucial. If you’re working on something related to EHR systems, you might find inspiration in (spam url removed by Jordan) to apply best practices.
Code: Select all
#if DEBUG
To fix this, start by reviewing the code in the
Code: Select all
#else
If the EHR code is exclusively for debugging purposes, consider refactoring it or ensuring that it doesn’t run in a release build. You can also implement fallback or alternative logic for the release build if needed. After making these changes, test both the debug and release builds to verify that everything works as intended.
For healthcare projects like this, structuring the code efficiently is crucial. If you’re working on something related to EHR systems, you might find inspiration in (spam url removed by Jordan) to apply best practices.
Re: Building for release, but EHR code generating errors
Not sure if you noticed or not, but this post is literally 14 years old 

Cheers,
Bill Starck, DDS
Big Idea Software, LLC
Developer, EASy(Electronic Anesthesia System) for Open Dental
817-807-1709
TX, USA
Bill Starck, DDS
Big Idea Software, LLC
Developer, EASy(Electronic Anesthesia System) for Open Dental
817-807-1709
TX, USA
- jordansparks
- Site Admin
- Posts: 5765
- Joined: Sun Jun 17, 2007 3:59 pm
- Location: Salem, Oregon
- Contact:
Re: Building for release, but EHR code generating errors
Yeah, pretty sure it's spam. Removing links until I can be sure.
Jordan Sparks, DMD
http://www.opendental.com
http://www.opendental.com