standard build env puts files in PCLBINDIR

[Nocturnal]

Hi,

contrary to how it used to be before the new makefiles put freshly built modules in PCLBINDIR. This is a problem because you can't just add a single module from PCLBINDIR. Once you search PCLBINDIR it'll find all modules that are part of the distro, somehow think they are new and then try to re-add them. This causes MetaModule redefinition problems, naturally.

So there seem to be two issues:

- modules that are already loaded are recognized as new, they should not
- the build environment writes output to PCLBINDIR rather than $PCLDIR/dist or something like that (the way it used to be)

I will change my VC project to copy the file to dist.

[Carlos Milovic]

looks like a bug in the new low level API, right?

[Nocturnal]

There's a problem in the makefiles that the PJSR script generates and possibly an issue in the framework. I don't think it's in PCL.

[Juan Conejero]

Hi Sander,

- the build environment writes output to PCLBINDIR rather than $PCLDIR/dist or something like that (the way it used to be)

New modules have always been copied to $PCLBINDIR by the MakefileGenerator script (take a look at older versions to verify). This is standard behavior. You don't have to re-install your module (using Process > Install Modules ...) each time you rebuild it. You just have to install it once. Then when you rebuild your module, a new -pxm.dll (or .so, or .dylib, depending on the platform) will be created and the next time you launch PixInsight Core the module will be installed as usual. This is the reason to copy newly built modules to $PCLBINDIR.

- modules that are already loaded are recognized as new, they should not

If this happens then we have a serious bug in PI Core (module installation subsystem). However I've just checked and this doesn't happen on Mac OS X (the only machine I have at hand now; I'm going to travel in about one hour). Please confirm that when you select Process > Modules > Install Modules > Search all already installed modules are recognized as new ones.

As a sanity procedure, I'd recommend uninstalling PixInsight, rebooting your machine, then making a fresh install.

[Nocturnal]

Hi Juan,

ok, perhaps not the makefilescript (which I've never used) but the makefiles that came with sandbox perhaps? I certainly did not make up the dist directory and my profile code did not use PCLBINDIR in the version I sent to you

Yes, I realize you only have to install modules one time. Clearly after spending (too) many hours writing module code this is something I noticed But I do have to add it in the beginning and that is when I noticed this behavior.

- uninstalled dist/Profile
- scan PCLBINDIR to pick up the Profile module where it was actually being put (I wasn't seeing changes in Profile at all so this led to the directory change discovery)
- tons of error dialogs as described

I can't reproduce this now so perhaps there was some other subtlty that I'm missing. No big deal.

I did notice that once I disable a module in Manage Modules and click done I can't re-enable it before restarting PI. I can change the check mark to green but the dialog doesn't allow me to press 'done'. Minor issue.