More on V4RB 4.8.1 apps crashing after install of V4RB 5.3.4

[Joseph Morgan]

When you say you're not using class way, do you mean that you are doing all/most of you're db access using SQL? 

> On Oct 10, 2013, at 2:59 PM, Steve Albin <steve at steve-albin.com> wrote:
> 
> To review, after installing V4RB 5.4.3 on my development computer, I cannot run (most) built apps that were created using V4RB 4.8.1.  Apps using V4RB 4.8.1 hard crash after opening the database.
> 
> Before, I mentioned that I had 3 apps using V4RB, but I realize I have 4.  I have also discovered that one app I have that is built using V4RB 4.8.1 will run on my machine after installing V4RB 5.4.3.  This app differs from my other apps in that I do not use the "class way" to open and access the database.  Otherwise, all coding techniques are pretty much the same.
> 
> I am not proficient in reading the Apple crash dumps, but in the list of Binary Images, I see this:
> 
> 0x2800000 -  0x28e6feb +libvshared_fat_release.dylib (4.8.0 - compatibility 4.8.0) <D6FA3D97-656B-5AA9-9A41-C5EB20C32DF3> /Applications/Brian.app/Contents/vcomponents/libvshared_fat_release.dylib
> 0x29b3000 -  0x2ec0ff3 +libvkernel_fat_release.dylib (4.8.0 - compatibility 4.8.0) <AEEFF4A4-E1DD-3D87-D93F-7F781599DB19> /Applications/Brian.app/Contents/vcomponents/libvkernel_fat_release.dylib
> 0x334a000 -  0x344dff7 +libvclient_fat_release.dylib (4.8.0 - compatibility 4.8.0) <D4E2684F-75B0-377F-2269-A69DECFB4E94> /Applications/Brian.app/Contents/vcomponents/libvclient_fat_release.dylib
> 0x354c000 -  0x3ba3fff +libvreport_fat_release.dylib (5.4.0 - compatibility 5.4.0) <9924F5FB-C65D-39B4-BA32-B41324BF6666> /usr/local/lib/vcomponents/libvreport_fat_release.dylib
> 0x3c85000 -  0x3debfeb +libvshared_fat_release.dylib (5.4.0 - compatibility 5.4.0) <1646F346-1954-3D0D-865F-9A22DFEA212A> /usr/local/lib/vcomponents/libvshared_fat_release.dylib
> 0x3ea6000 -  0x4029ff3 +libvclient_fat_release.dylib (5.4.0 - compatibility 5.4.0) <4CD1E6E3-E1BA-3807-9F2F-C9E0FF66A8AF> /usr/local/lib/vcomponents/libvclient_fat_release.dylib
> 0x4113000 -  0x4808ff3 +libvkernel_fat_release.dylib (5.4.0 - compatibility 5.4.0) <62F04353-F33B-386F-9F36-E4C7C10E7BE4> /usr/local/lib/vcomponents/libvkernel_fat_release.dylib
> 
> 
> It appears that my app is accessing .dylib from two different versions of Valentina.  Bear in mind that these apps have been working fine for years.  The only thing that changed for me is that I installed a newer version of Valentina on my computer.  I have no idea why my app should be looking at the /usr/local/lib/vcomponents/ folder at all.  Is there a way to prevent this?
> 
> I thought that our apps would use the libraries that we bundle with them using the deployment script, but evidently, they look for newer libraries on the host computer.  
> 
> Again, these are apps built and shipped long before I had V4RB installed on my computer.  If this is the case, theoretically no Valentina developer can use my apps unless they are using the same version of Valentina I used to build the app.  (Big deal, they say!) 
> 
> Can I get a confirmation that this is the case?  Do I need to Mantis this?  In some respects, I don't care much because I'm going to upgrade all my apps to the newer version of V4RB, but I'd like to know if my understanding is correct.
> 
> Steve
> 
> --
> Steve Albin, Montclair, NJ
> http://www.steve-albin.com
> http://www.jazzdiscography.com
> 
> _______________________________________________
> Valentina mailing list
> Valentina at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina