Not so smooth upgrade.

Everything else that doesn't fall into one of the other PB categories.
jassing
Addict
Addict
Posts: 1885
Joined: Wed Feb 17, 2010 12:00 am

Not so smooth upgrade.

Post by jassing »

I installed the upgrade to 4.61 -- now when I try to build a project, I get this:

Code: Select all

--------------------------------------------------------------------------------
  Building 'Installer Toolkit'...
--------------------------------------------------------------------------------

[i][b]<snipped file list>[/b][/i]

9896 lines compiled.
Creating executable file...
Resource error
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(1): warning: Macro redefinition of 'VOS_UNKNOWN'.
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(2): warning: Macro redefinition of 'VOS_DOS'.
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(3): warning: Macro redefinition of 'VOS_OS216'.
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(4): warning: Macro redefinition of 'VOS_OS232'.
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(5): warning: Macro redefinition of 'VOS_NT'.
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(6): warning: Macro redefinition of 'VOS_DOS_WINDOWS16'.
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(7): warning: Macro redefinition of 'VOS_DOS_WINDOWS32'.
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(8): warning: Macro redefinition of 'VOS_OS216_PM16'.
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(9): warning: Macro redefinition of 'VOS_OS232_PM32'.
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(10): warning: Macro redefinition of 'VOS_NT_WINDOWS32'.
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(11): warning: Macro redefinition of 'VFT_UNKNOWN'.
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(12): warning: Macro redefinition of 'VFT_APP'.
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(13): warning: Macro redefinition of 'VFT_DLL'.
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(14): warning: Macro redefinition of 'VFT_DRV'.
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(15): warning: Macro redefinition of 'VFT_FONT'.
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(16): warning: Macro redefinition of 'VFT_VXD'.
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(17): warning: Macro redefinition of 'VFT_STATIC_LIB'.
PORC: C:\Documents and Settings\Josh\Local Settings\Temp\PB_Resources.rc(19): fatal error: Can't find include file C:\temp\resourcetest.rc.

--------------------------------------------------------------------------------

  1 targets compiled with errors.
I do not show anything that references "c:\temp" anything...
IdeasVacuum
Always Here
Always Here
Posts: 6426
Joined: Fri Oct 23, 2009 2:33 am
Location: Wales, UK
Contact:

Re: Not so smooth upgrade.

Post by IdeasVacuum »

What is the install path used for PB4.61? Does it have it's own unique folder in C:\Program Files?
Would be best to install to, say, C:\Program Files\PureBasic461 rather than overwrite the previously installed version.
IdeasVacuum
If it sounds simple, you have not grasped the complexity.
jassing
Addict
Addict
Posts: 1885
Joined: Wed Feb 17, 2010 12:00 am

Re: Not so smooth upgrade.

Post by jassing »

IdeasVacuum wrote:What is the install path used for PB4.61? Does it have it's own unique folder in C:\Program Files?
Would be best to install to, say, C:\Program Files\PureBasic461 rather than overwrite the previously installed version.

So each new version of purebasic isn't really an upgrade, it's a new program -- makes sense with how userlibraries are (not) supported ...

thanks, i'll do that.
IdeasVacuum
Always Here
Always Here
Posts: 6426
Joined: Fri Oct 23, 2009 2:33 am
Location: Wales, UK
Contact:

Re: Not so smooth upgrade.

Post by IdeasVacuum »

I use a few libs, they are all '4.60' and seem to be working fine with 4.61.

I think a clean install of PB always works best (perhaps an essential file does not get overwritten etc) - plus of course, if it transpires that the new has a howler, reverting back to old is a snip.
IdeasVacuum
If it sounds simple, you have not grasped the complexity.
Post Reply