Ticket #77 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

Set OSG_DEBUG

Reported by: dirk Assigned to: anonymous
Priority: critical Milestone: 2.0 Beta
Component: Build Version: 2.0
Keywords: Cc:
Completion:

Description

OSG_DEBUG needs to be set depending on which kind of build is being done.

Change History

(follow-up: ↓ 2 ) 10/04/06 09:10:56 changed by allenb

  • owner changed from unassigned to anonymous.
  • priority changed from major to critical.
  • version set to 2.0.
  • status changed from new to assigned.

What things will this variable influence?

- Is it safe to only set when building the libraries? - Does it influence class layout? - Does it influence anything in header files? - When a user compiles an application debug will they expect the code influenced by this flag to be enabled?

(in reply to: ↑ 1 ) 10/04/06 18:45:54 changed by dirk

Replying to allenb:

What things will this variable influence? - Is it safe to only set when building the libraries?

Yes.

- Does it influence class layout?

No.

- Does it influence anything in header files?

It might, but nothing that has an impact on user code.

- When a user compiles an application debug will they expect the code influenced by this flag to be enabled?

Yes and no. The only user-visible thing I can think of right now is that FDEBUG output is ignored with OSG_DEBUG is not set. Everything else should be the same. The main thing is that using the debug libs will have code that is compiled with this flag active.

10/06/06 16:28:25 changed by allenb

  • status changed from assigned to closed.
  • resolution set to fixed.

Fixed in r247.

10/06/06 16:29:08 changed by allenb

Oops, I mean r249