Dear friends,
I want to make two different library ( .mcl file) for two different MCUs by giving a same library Alias and want to put in to a same Package (as libraries provided by MikroC).
For example I want to put two files "Lib_ADC_1.mcl" and "Lib_ADC_2.mcl" for P12f683 and P18F2550 respectively with a same library alias "ADC" under the package named " My_ custom" and want to install in to MikroC IDE with the tool Package manager for displaying same alias name "ADC" in the Library manager window under the package node "My_ custom" in MikroC IDE for the both MCUs .
But problem aeries is that the Package Manager do not allow to include both ".mcl" file in to a single library. If I will make two different library for both ".mcl" file in the same package, the Package Manager do not allow to give same alias name for both library.
If I will make two different library by giving two different alias in the same package for the different selected MCUs and install in to MikroC IDE the Library Alias chances at the package " My_ custom" sub node in the Library manager window, when I change the MCU in Project Settings window. Then how it is possible that these two libraries have the same Library Alias (ADC).
If it is not possible, how all libraries provided by MikroC with same alias for different MCUs.
Problem to give a same Library Alias for different PICs .
Re: Problem to give a same Library Alias for different PICs
Obviously it's possible, though mE doesn't use the Package Manager for official libraries (or they couldn't do the trick 
). Unfortunately, Package Manager uses library name (that later becomes library alias in processor definition files) to discern between libraries and thus won't allow to have different libs with the same name.
You may either manually change respective processor definition files and place the libraries in P16 and P18 folders (every new compiler version will destroy them, though), or prepare two separate packages.
). Unfortunately, Package Manager uses library name (that later becomes library alias in processor definition files) to discern between libraries and thus won't allow to have different libs with the same name.You may either manually change respective processor definition files and place the libraries in P16 and P18 folders (every new compiler version will destroy them, though), or prepare two separate packages.
Re: Problem to give a same Library Alias for different PICs
Very very thanks for clarification.
Re: Problem to give a same Library Alias for different PICs
You're welcome 
. I think that Package Manager modification constituting a solution to your problem would make a reasonable request. There are many situations that require small library adaptation to different processors and the way Package Manager works now prevents preparing user libraries with processor-dependent variations. Adding a 'library alias' field and using it when modifying processor definition files (instead of library name) would make the above possible.
. I think that Package Manager modification constituting a solution to your problem would make a reasonable request. There are many situations that require small library adaptation to different processors and the way Package Manager works now prevents preparing user libraries with processor-dependent variations. Adding a 'library alias' field and using it when modifying processor definition files (instead of library name) would make the above possible.