Revision history [back]

yes, changes going on there. errors being made, too.

it seems the module headers ( as in api/client ) are moved one up, so it's

opencv2/core.hpp opencv2/highgui.hpp

etc.

2 weeks ago, the cmake-generated install script would still (correctly) copy the headers in this way, but it seems broken now ( fetched 3 days ago )

my current workaround for my own projects depending on opencv is:

regenerate proj/solution file using cmake this will add the includes of the modules, not the ones from install/build

don't use opencv.hpp, but the explicit module headers instead, opencv2/core.hpp, opencv2/highgui.hpp, etc

yes, changes going on there. errors being made, too.

it seems the module headers ( as in api/client ) are moved one up, so it's

opencv2/core.hpp opencv2/core.hpp

opencv2/highgui.hpp

etc.

2 weeks ago, the cmake-generated install script would still (correctly) copy the headers in this way, but it seems broken now ( fetched 3 days ago )

my current workaround for my own projects depending on opencv is:

 
regenerate proj/solution file using cmake this will add the includes of the modules, not the ones from install/build
install/build
 
don't use opencv.hpp, but the explicit module headers instead, opencv2/core.hpp, opencv2/highgui.hpp, etc

yes, changes going on there. errors (errors being made, too.made probably, too.)

it seems the module headers ( as in api/client ) are moved one up, so it's

opencv2/core.hpp

opencv2/highgui.hpp

etc.

2 weeks ago, the cmake-generated install script would still (correctly) copy the headers in this way, but it seems broken now ( fetched 3 days ago )

my current workaround for my own projects depending on opencv is:

1. regenerate proj/solution file using cmake this will add the includes of the modules, not the ones from install/build

2. don't use opencv.hpp, but the explicit module headers instead, opencv2/core.hpp, opencv2/highgui.hpp, etc

yes, changes going on there. (errors being made probably, too.)

it seems the module headers ( as in api/client ) are moved one up, so it's

opencv2/core.hpp

opencv2/highgui.hpp

etc.

2 weeks ago, the cmake-generated install script would still (correctly) copy the headers in this way, but it seems broken now ( fetched 3 days ago )

my current workaround for my own projects depending on opencv is:

1. regenerate proj/solution file using cmake this will add the includes of the modules, not the ones from install/build

2. don't use opencv.hpp, but the explicit module headers instead, opencv2/core.hpp, opencv2/highgui.hpp, etc

yes, changes going on there. (errors being made probably, too.)

it seems the module headers ( as in api/client ) are moved one up, so it's

opencv2/core.hpp

opencv2/highgui.hpp

etc.

2 weeks ago, the cmake-generated install script would still (correctly) copy the headers in this way, but it seems broken now ( fetched 3 days ago )

my current workaround for my own projects depending on opencv is:

1. regenerate proj/solution file using cmake this will add the includes of the modules, not the ones from install/build

2. don't use opencv.hpp, but the explicit module headers instead, opencv2/core.hpp, opencv2/highgui.hpp, etc